They probably found some silly anti-pattern they were doing previously that was killing performance for no good reason.
The entire history of npm screams "we're pretty much learning all of this as we go, please bear with us".
While there's nothing wrong in that (people have to learn somehow) it does make it very, very hard to put any trust in that project. Especially when said project is at the very center of an entire ecosystem, it makes it hard to trust the ecosystem as well. I'm already seeing a lot of good developers move away from node as they gain experience and realize things should be much better.
Its pretty much standard for literally any project I've seen without senior devs to see these bugs before a release.
The entire history of npm screams "we're pretty much learning all of this as we go, please bear with us".
While there's nothing wrong in that (people have to learn somehow) it does make it very, very hard to put any trust in that project. Especially when said project is at the very center of an entire ecosystem, it makes it hard to trust the ecosystem as well. I'm already seeing a lot of good developers move away from node as they gain experience and realize things should be much better.
Its pretty much standard for literally any project I've seen without senior devs to see these bugs before a release.