right! it's the height of entitlement and childishness. Which makes sense — I can't think of anything more immature and less constructive thanhttps://github.com/staltz/prevent-smoosh …
-
-
Replying to @Rich_Harris @AdamRackis
It deeply concerns me that many dev advocates, who I would think would view themselves as shepherds of the open & compatible web, are advocating for this change and ripping on people who believe in preserving the books.
2 replies 0 retweets 2 likes -
Replying to @danbucholtz @Rich_Harris
Oh man my respect for the "developer advocate" position's been free falling in past years. They always seem to work for major corporations who profit from search engines, and their advice seems to ALWAYS be narrowly focused on maximizing their profits from said search engines.
2 replies 0 retweets 3 likes -
-
I am honestly shocked that this issue is the one that triggered a revolt. TC39 has a large number of people who write web apps and websites every day, at big companies and small. And we know how to break things if warranted.
2 replies 1 retweet 7 likes -
Replying to @wycats @danbucholtz and
The major issue I have is MooTools isn’t in wide use. And while it was used in the past, we shouldn’t be afraid to break a decade-old mostly defunct library. If we are, we become Microsoft with tons of cruft polluting our eco-system.
3 replies 0 retweets 0 likes -
Replying to @ClashCityKing @wycats and
at the scale of the web, a fraction of a percentage means hundreds of thousands of sites
2 replies 0 retweets 1 like -
Replying to @Rich_Harris @wycats and
That very well may be totally outdated and unused. Neither you nor I can say if it’s important those sites are available.
1 reply 0 retweets 0 likes -
Replying to @ClashCityKing @Rich_Harris and
I'd say existing sites being available is a lot more important than JS devs getting their first choice for method names.
1 reply 0 retweets 0 likes -
Replying to @AdamRackis @Rich_Harris and
I get that’s your position and I acknowledge it’s valid but I disagree with it and think this specific statement is over simplification
1 reply 0 retweets 0 likes
I think it depends on the consequences. Array.prototype.contains -> Array.prototype.includes had no meaningful impact on usability, so it was more or less a slam dunk. flatten -> smoosh() is much worse so the tradeoff isn't worth it. The details matter.
-
-
Replying to @wycats @AdamRackis and
100% agree. If we can find a sensible alternative, great let’s do that. “smoosh” is not sensible. I would also say we can weigh impact. Impacting sites built on MooTools is acceptable in 2018.
0 replies 0 retweets 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.