We're not talking about destroying the work of the people who were Told™. We're talking about destroying (the only copy of) the work of authors whose publishers (unwittingly, in many cases) used the wrong paper.https://twitter.com/brianmfitch/status/971770091665752064 …
-
-
Replying to @Rich_Harris
Authors may not be reachable. Oh, and this stupid fucking ventilation system ***doesn't even*** protect the books better. Some douchebag engineers just happen to think it looks cool. Authors will be forgiven for telling the engineers to fuck right off, and not damage the books.
1 reply 0 retweets 2 likes -
Replying to @AdamRackis
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 …
1 reply 0 retweets 10 likes -
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 @danbucholtz and
Honestly, that's just abstract rhetoric. I don't think it was a big deal for us to change Array.prototype.contains to Array.prototype.includes, and don't think that means we "became Microsoft" or "added cruft". We make decisions based on cost-benefit, and try not to break.
2 replies 0 retweets 1 like
Turning "we try hard not to break" into a broadly morally suspect position strikes me as overheated rhetoric. That said, smoosh() is a bad name for this API.
-
-
Replying to @wycats @danbucholtz and
Trying hard not to break is over-broad and means many things. It’s not specific enough to be actionable.
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.