[diggan]

> They don't change because there is some other thing that is supposedly better. It has to be 10x better before people will migrate off one thing to another.

That's the point, and it makes sense from their perspective, I'd probably do the same as well.

Creating a new library instead of changing the existing one lets people chose between those two approaches. Want the latest and greatest but with API breakage? Use this library. Wanna continue using the current API? Use this library.

Instead, we kind of force the first approach on people, which I personally aren't too much of a fan of.

[skydhash]

As I’ve said in other comments. If you’re developing a library, you can commit to its API and do security and optimization fixes and build a new one where you try a new design/approach. Merging the two together is always a bad idea.