We've banned this account for what should be obvious reasons.
If you don't want to be banned, you're welcome to email hn@ycombinator.com and give us reason to believe that you'll follow the rules in the future. They're here: https://news.ycombinator.com/newsguidelines.html.
Specific to this article they're saying "the Republican special prosecutor has good reasons to do this (that aren't political)" to cut that argument off.
> This will also reduce the fraction of developers trying to micro-optimize already fast selectors.
I always feel like browser devs regularly look at the web naively and think "yeah nobody should waste time optimizing for that", but then you get sites having 800kb of CSS and lots of terrible selectors and you have no tools to analyze them besides generic coverage.
Personally, I've never felt overwhelmed by choice when it comes to options regarding optimization. It's fine if it's hidden behind a flag, but "nobody could ever need this" feels weird.
Slightly exaggerated numbers there, but how bad can a css selector really be to the client experience when it's likely based on today's UI dev trends that we're loading 3mb of react + other JS
I wish I was exaggerating, that's something I recently had to deal with :(
You're right, "I need an OS written in JS to run before I can toggle that menu" dwarfs all of it. I'm lucky in that regard, I usually deal with jQuery-based things; you can still trim 95% of the code if you got rid of it (carousels are stopping me, people love carousels), but even if you don't, you land at like 100kb JS and you can defer it.
The reason is that Apple wants a cut of the Spotify subscription money when users sign up for Spotify on an iOS or iPadOS device. IMHO, it's a bad look for Apple. They should either get out of the music business or stop taking a cut of the money from apps that compete with Apple services.
