I'm planning to keep the basic, most used APIs the same, but yes, there will be some breaking changes. Promises will follow ES6 API and advanced redraw control APIs will likely be changed to improve ergonomics and leverage good ideas from other vdom libraries.
Other correct comments about a quite active 'next' branch aside... The latest commit on master is Nov 12, 2015. That's not even half a year ago. The stable shelf life of software worth mentioning is longer than that, don't you think?
> That's not even half a year ago. The stable shelf life of software worth mentioning is longer than that, don't you think?
I can see that you haven't spent much time in the JavaScript ecosystem. And forget latest commit, if a JS project wasn't started in the last half year, it's already getting long in the tooth. After a half year, trendy devs will already start moving on to the next great framework and package manager.
Yes, that is my point, with so many options in JS frameworks, libs, etc, I normaly study Github activity before jumping in. Learning a new tool takes time and we cannot afford to waste it on dead-end projects.
Yes of course, but I would expect many commits between stable releases (patching issues). I guess this is just a different pattern where a solo-dev goes quitely working for a few months and then emerges with the next release.
To give some context, even though the version is at 0.2.x, it's been fairly stable for months, and there have been very few bug reports (despite it being used fairly extensively in relatively big codebases - see lichess.org, for example).
Most of the "bugs" (or rather, limitations) in the issue tracker are either discussions or things that are difficult to address w/ the current codebase - e.g. design/ergonomics issues, as opposed to implementation issues - Those are part of the reason for the rewrite.
Another thing that is worth mentioning is that Mithril's general philosophy is to avoid adding features for features' sake, so it can look less "active" than it actually is.
