JavaScript boy and “lovely thoughtleader” 
he/him 
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
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?
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 …
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
If a JS engine implements behaviour that's different than the spec, then it's not JavaScript.
ES5 spec says specifically that order is not guaranteed.
Semi-standard - nothing false about a de facto partial standard.
“Before that it was pseudo-standard”. Browsers have done it for a loooong time.
But if the misconception is so common that means relying on it is against the principle of least astonishment. People will reorder properties and expect things to still work. There are literally lint rules that enforce alphabetic property order
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
