322 karma · joined December 1, 2024
Needs a comparison to Vite/esbuild though. The docs only mention Webpack, but idk who's using Webpack on new projects in 2025. There's a benchmark that includes Vite on the homepage, but that's not gonna be enough to get me to switch to a newcomer with a smaller community unless there's some usability difference too.
The CSS support also needs a comparison to LightningCSS (which Vite also supports and has some advantages over esbuild), especially when it comes to bleeding-edge features like view transitions and nesting.
Dev's complaint: https://github.com/microsoft/vsmarketplace/issues/1173
Apparently that extension had 5M installs prior to being removed.[0] It was only just released in 2021, btw; there's another Material Icon Theme you might be thinking of that's been around since 2016 and has 28M installs.[1]
[0]: https://web.archive.org/web/20241220084427/https://marketpla...
[1]: https://marketplace.visualstudio.com/items?itemName=PKief.ma...
We've come full circle
If anyone wants a similar tool for Windows that does the OCR locally instead, I recommend Text Grab (https://github.com/TheJoeFin/Text-Grab).
Not to mention, if you revoke a key (maybe because you lost your laptop and want to be proactive about security), without any authenticated timestamping service in the mix, all past messages and signatures can no longer be trusted, regardless of the revocation date. That's why when you revoke a key on github, all your previous commits' signatures turn red.
I've never understood why no one's succeeded in doing anything about this after all these years.
This is what makes me afraid for the future of software development. Even in this thread you see people saying they "don't write css and just let the ai do it." I don't think I could work for a company where the devs don't understand the language and just have chatgpt poop out blocks of code until it works, but we're starting to see exactly that now. And worse: they're proud of it. It's terrifying.
The correct thing to do here is put a caching layer in front so that every feed reader isn't simultaneously hitting the origin for the same content. IP banning is the wrong approach. (Even if it's only a temporary block, that's going to cause my reader to show an error and is entirely unnecessary.)
My problem with the Bravia TV I have is it takes a solid minute for the Android system to boot up, so I can't just put it on a smart plug and expect it to turn on when I turn it on...