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

@wallhackio if coriander sees this post i feel like it will rewaken their hater energy

https://x.com/suna_k0nbu/status/1813517440862871691/

@Lady huh

@Lady @Satsuma ​

@Lady @Satsuma j i regret to tell you that is not a flabébé

@Satsuma @Lady puppy???

@wallhackio look in the mirror, Unaware what you see

@wallhackio

full of aspurrin -> ​

@wallhackio can you PLEASE give me that non-angy distressed clod

@wallhackio holy shit

@wallhackio this would be a great emojo

@wallhackio u when u have a slight headache all day

@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