> Even mithril.js isn't completely dead.
That's a rather un-generous description of a framework under active development with an active community.
A lot of code is 1-2 years old.
Though I'm happy that mitrhil.js lives and is being developed (not just maintained). I only wish it wider adoption.
The "not completely dead" was meant to be somehow tongue-in-cheek.
v2.0 is coming. Breaking changes are minor stuff. Migration of my very large app took me about an hour. The API of mithril is pretty much settled, which IMO is a good thing. We even plan to remove stuff for next major. Simplicity is key.
Sad, though. A framework can afford a lot of technical debt, but adding more conceptual debt, like React was doing recently, seems to me like a road to oblivion^W legacy status. Features that lack clarity and come bundled with footguns tax developer's brain resources, and increase the rate of errors. These are some of the most expensive resources in IT, and fighting errors lengthens time to market.