Relying on object property order for a styling API. Good or bad? eg. styles({ backgroundBlue: true, backgroundRed: true, }); In this case the background would be `red` as it appears last. Relying on property order feels gross but can't think of a better API?
-
Show this thread
-
Want to clarify a common misconception that JS does not have a guaranteed property order. It does. In fact it was standardised in ES2015. Before that it was a pseudo-standard among most engines. See https://tc39.github.io/ecma262/#sec-ordinaryownpropertykeys …
20 replies 36 retweets 169 likesShow this thread -
Replying to @sebmck
Is this a strong "this will never get removed" thing? I can imagine some peeps being like "we don't need this" creating a war between js factions
2 replies 0 retweets 0 likes
Replying to @selfiesticarus
If a JS engine implements behaviour that's different than the spec, then it's not JavaScript.
12:12 PM - 16 Oct 2018
0 replies
0 retweets
12 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
he/him 