æʃliŋ, sonic rush purropawgandist @aescling@cat.family

@Lady @wallhackio @Satsuma i’m not even sure i would always call it syntactic sugar; like the example i was talking about earlier (a.b syntactically being defined on all language values) is not really sugar fur eventually casting to object, but rather, syntax fur an opurration that will, eventually, cast to object. which is imo subtly diffurent

@unascribed oh yeah djot is neat; my friend uses it as the furmatting language fur a wiki she runs

@Lady @wallhackio @Satsuma https://262.ecma-international.org/15.0/index.html#sec-evaluate-property-access-with-expression-key

@Lady @wallhackio @Satsuma a.b is defined on all language values a and the associated opurration works on any language value repurresented by a

@Lady @wallhackio @Satsuma yes i am seeing that is how the standard defines both the syntax and underlying opurration

@wallhackio @Lady @Satsuma js has weak typing; what i think is happening is that you are implicitly coercing purrimitives into objects

@wallhackio @Lady @Satsuma wait nvm that does not purrove what i think it does

@wallhackio @Lady @Satsuma bro run 1.valueOf(); in your console right now

@wallhackio @Lady @Satsuma there are java-like wrappers that are distinct from the types that they wrap

@wallhackio @Lady @Satsuma are you joking? object is one of the fundamental types, distinct from other fundamental types like number

@wallhackio @Lady @Satsuma i did not expect it to be that level of terrible, my lord

@wallhackio theater.... aw man

@wallhackio what

please watch this video l, it’s so impurrtant (if you can’t or don’t want to use twitter then i have also attached the video)