lhorie and smuemd, thank you for the additional detail, but as a non-Mithril user I still don't understand the big picture.

For example, Vue 2.0's announcement[1] made clear that the release was about performance, new render functions enabling new component-based patterns, and server-side rendering.

What's going to "wow" Vue and React users who haven't looked at Mithril?

[1] https://medium.com/the-vue-point/vue-2-0-is-here-ef1f26acf4b...

Honestly, none of the 2.0 stuff is really all that interesting to an outsider. And ironically, often times the "wow" factor of other frameworks are old news to Mithril users. Mithril has had "modern" "zero-cost" features like closure components (similar to the recent svelte v3 data "API") for years. Some things _still_ don't exist in major frameworks (e.g. css selector support in hyperscript API, lifecycle hooks in fragments, or as event handlers, or true POJO-as-a-global-data-store support).

In my opinion the Mithril community is only mildly interested in evangelizing Mithril. They're much more interested in coding. To such a community, breaking changes that improve code are the wow factor.

Mithril uses Semantic Versioning (https://semver.org/) if I recall correctly. All the 2.0 signifies is that there are major breaking changes. If you're curious about those changes, take a look at the changelog: https://mithril.js.org/change-log.html#v200

Otherwise, the "big picture" hasn't changed since the v1 release. Mithril is a lightweight alternative to those frameworks that provides routing, auto-redraw, closure components, XHR utilities, reactive streams, and a testing framework out of the box. The v2 release has less to do with gaining market share or generating hype than it does refining an already great tool.

> What's going to "wow" Vue and React users who haven't looked at Mithril?

That doesn't seem to be covered by the release announcement, but is addressed here:

https://mithril.js.org/framework-comparison.html

This helps contextualize Mithril a lot, thank you!