What the *smoosh* happened to Array#flatten?! Why is everyone talking about MooTools? Why doesn’t TC39 just break the Web?
@mathias explains #SmooshGate:https://developers.google.com/web/updates/2018/03/smooshgate …
-
-
Replying to @ChromiumDev @mathias
craig martin Retweeted craig martin
"'don’t break the Web' is the number one design principle for ... JavaScript" Why?https://twitter.com/thecraigmichael/status/972201451677155329 …
craig martin added,
craig martin @thecraigmichaelReplying to @BenLesh @Rich_Harris @_jayphelpsBut is it the prerogative of TC39 to be guardians of The Web, or of the ECMAScript language? Wouldn't it seem like the right place to address userland business logic is in that page's codebase - OR, if the browsers have a stake in One Web, at that layer?https://twitter.com/thecraigmichael/status/972195533430370309 …1 reply 0 retweets 0 likes -
For the reasons listed in https://developers.google.com/web/updates/2018/03/smooshgate#break-the-web …
2 replies 0 retweets 3 likes -
Does it strike you as odd that a *language* specification committee is beholden to userland business logic - something with limited visibility on a non-web platform, eg node - as a contract, and not a set of well defined principles?
2 replies 1 retweet 1 like -
Replying to @thecraigmichael @jaffathecake and
It's such biased totalistic absolutist brow-beating to phrase it as "why don't we break the web?". It's nasty. It already has the knife in your heart before you even finish making your argument. So meanspirited.
1 reply 0 retweets 1 like -
Replying to @rektide @thecraigmichael and
If we add ANYTHING to JS we probably break some website somewhere. Knowing is more or less impossible. Do we know how many MooTools 1.2 & before website there are? Can we find 500? 100? How much breakage are we talking about?
2 replies 0 retweets 0 likes
I agree telemetry is hard, as https://developers.google.com/web/updates/2018/03/smooshgate#removing-apis … mentions. But when browser vendors are getting bug reports after shipping a new feature, it’s a pretty strong signal that the feature may not be Web-compatible. I don’t follow what’s so disgusting about this explanation.
-
-
Replying to @mathias @thecraigmichael and
I don't think adding anything to JavaScript core prototypes is web compatible in this model. The unwillingness to even permit the distinction of whether web compatibility has to afford for every single dolt who monkeyed with the global namespace is madness.
0 replies 1 retweet 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.