3 ms·
The problem is jest is run by megacorp Meta, so it won't be fixed in any reasonable timeframe because they're all about new features to make "impact". Its FOSS
by pcb-rework 2y ago
The problem is jest is run by megacorp Meta, so it won't be fixed in any reasonable timeframe because they're all about new features to make "impact". Its FOSS contributors are typically slow and working primarily to keep their jobs. Also, with node > 20.9.0 being broken and node = 20.9.0 not being a viable option by being insecure, so it's worth having a look at alternatives like bun or deno because it does seem to have lost its way too. I'm currently pinned to 20.9.0 for system dependencies, but use bun for new dev.
- cowsandmilk 2y agoAs described in the article, Jest is no longer run by Meta and its primary maintainers don’t work there. I also would argue Jest development slowed down after Meta transferred the project to OpenJS, so…
- pcb-rework 2y ago> Please don't comment on whether someone read an article. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html A rotten apple doesn't roll far from the tree. The vast majority of Meta projects and former projects are garbage. If you need to ask why, because it's experience.