3 ms·

Over time, a few things were identified that would require a breaking change to improve. These changes have to happen at some point, and the 2.0 milestone is th

by lhorie 7y ago

Over time, a few things were identified that would require a breaking change to improve. These changes have to happen at some point, and the 2.0 milestone is that. The community agreed that a big bang major release makes migration easier than many disjointed breaking changes mixed with other bug fixes of various priorities. Prior to this release, the Mithril team went through painstaking troubles to release RCs to help consumers prepare for the breaking changes and find issues before the official version bump. Now that the code is deemed stable, the 2.0 milestone simply formalizes that the major version bump is now official.

CharlesW 7y ago
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-ef1f26acf4b8 https://medium.com/the-vue-point/vue-2-0-is-here-ef1f26acf4b...
- brlewis 7y ago
  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.
- keb_ 7y ago
  Mithril uses Semantic Versioning (https://semver.org/ 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 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.
- lhorie 7y ago
  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).
- dragonwriter 7y ago
  > 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 https://mithril.js.org/framework-comparison.html
  - CharlesW 7y ago
    This helps contextualize Mithril a lot, thank you!

by lhorie 7y ago

CharlesW 7y ago

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-ef1f26acf4b8 https://medium.com/the-vue-point/vue-2-0-is-here-ef1f26acf4b...

brlewis 7y ago
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.
keb_ 7y ago
Mithril uses Semantic Versioning (https://semver.org/ 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 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.
lhorie 7y ago
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).
dragonwriter 7y ago
> 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 https://mithril.js.org/framework-comparison.html
- CharlesW 7y ago
  This helps contextualize Mithril a lot, thank you!