The initial selling point was performance, but then they gradually realized that a lot of the slow cruft in Jest was necessary for correctness, and now it's about the same performance as Jest (obviously may vary in some specific situation).
However vitest is still great! Selling points now are stuff like:
- shares config with vite
- works with ESM out of the box (I think Jest still doesn't)
- integrated browser testing mode that is very nice
- overall just has a ton of nicely integrated features
Well there is a permission dialog and you need to select the directory to grant access and common sensitive directories are blacklisted.
A malicious ad would probably have an easier time tricking you into downloading and running an executable, which is something that has actually happened many times IRL. Worry about that before worrying about theoretical exploits that nobody has actually exploited in an API shipped in the world's most popular web browser for the past 6 years.
So what should I do if I want to make an app with this functionality? Do I have to tell users to download and run some executable? You can imagine a case where that is a bit riskier than a nicely sandboxed web app with permission to access one directory.
It is a great API though, I wish the other browser vendors liked it! Because currently us PWA developers are really limited when trying to make apps that work with local data, at least in non-Chrome browsers.
That's exactly what they did at my college (non-California state school) 20 years ago. Special program for students from poor high schools who otherwise wouldn't be admitted, where they came in the summer before freshman year and had to pass some prep classes first. IDK what the actual long term results were, but seems like a better idea than nothing.
The tests will be made by AI as well, because professors who spend less time on making tests can spend more time on research and get hired/promoted more. For the same reason, professors won't care who is using AI to cheat on the test that was made by AI. Maybe some people will care, but not enough to do anything about it.
(Cheating was already rampant in many classes 20 years ago when I was in college, I can't imagine what it's like now.)
Yeah I have one semi-popular package and I am still doing local publish with 2fa because all this "trusted publishing" stuff seems really complicated and also seems to get hacked constantly. Maybe it's just too complicated for us to do securely and we should go back to the drawing board.
But in practice, nobody (well, nobody making lots of ad revenue from their website) uses AdSense exclusively. Most don't even use it at all - AdX is better as a header bidding fallback than AdSense. But those who do use AdSense as a fallback are using it in competition with many other ad networks.
In practice there's this one guy who likes to support ancient JS engines, and this one other guy who likes making lots of tiny packages which depend on his other tiny packages. They both see what they're doing as features, not bugs. And they are both very prominent devs with a lot of popular packages.
So unlikely to change unless everyone stops using their popular packages.
Every now and again people get worked up and try to bully them about it, which is unfortunate because they seem like generally good people, and their arguments in favor of their positions are pretty well documented.
The article says the city claims the biggest issue is federal regulations (the ADA) not city regulations.
My neighborhood in NJ just got those fancy ADA compliant curb ramps last year, along with a repaving. It did take them much longer to install the curb ramps (like a week or two?) than it did to pave (one day) so I can imagine there is a significant cost, even if it's a smaller amount of materials.
Back when I had a job at a big old corporation, a significant part of my value to the company was that I knew how to bypass their shitty MITM thing that broke tons of stuff, including our own software that we wrote. So I could solve a lot of problems people had that otherwise seemed intractable because IT was not allowed to disable it, and they didn't even understand the myriad ways it was breaking things.
However vitest is still great! Selling points now are stuff like:
- shares config with vite
- works with ESM out of the box (I think Jest still doesn't)
- integrated browser testing mode that is very nice
- overall just has a ton of nicely integrated features