Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Mithril.js 2.0 Released

github.com

Post reply on HN
Print view View original

11–20 of 20 posts

Re: Mithril.js 2.0 Released

#11

Post by lhorie »

CharlesW wrote: post #3

This seems like a significant release, so it's a shame that there's nothing in the changelog or on the interwebs at large that tells me why it matters. Does anyone know?

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.

Re: Mithril.js 2.0 Released

#12

Post by CharlesW »

lhorie wrote: post #11
CharlesW wrote: post #3

This seems like a significant release, so it's a shame that there's nothing in the changelog or on the interwebs at large that tells me why it matters. Does anyone know?

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 he…

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...

Re: Mithril.js 2.0 Released

#13

Post by brlewis »

CharlesW wrote: post #12
lhorie wrote: post #11

Earlier quoted context omitted.

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 he…

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-i…

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.

Re: Mithril.js 2.0 Released

#14

Post by toastercat »

CharlesW wrote: post #12
lhorie wrote: post #11

Earlier quoted context omitted.

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 he…

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-i…

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.

Re: Mithril.js 2.0 Released

#15

Post by lhorie »

CharlesW wrote: post #12
lhorie wrote: post #11

Earlier quoted context omitted.

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 he…

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-i…

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).

Re: Mithril.js 2.0 Released

#16

Post by dragonwriter »

CharlesW wrote: post #12
lhorie wrote: post #11

Earlier quoted context omitted.

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 he…

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-i…

> 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

Re: Mithril.js 2.0 Released

#17

Post by CharlesW »

dragonwriter wrote: post #16
CharlesW wrote: post #12

Earlier quoted context omitted.

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-i…

> 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!

Re: Mithril.js 2.0 Released

#18

Post by oceanghost »

grzm wrote: post #10
oceanghost wrote: post #9

Can someone explain what Mithril is and why I might want it? Not a troll.

https://github.com/MithrilJS/mithril.js/blob/next/README.md#... > ”What is Mithril?” > ”A modern client-side Javascript framework for building Single Page Applications. It's small (9.55 KB gzipped), fast and provides routing and XHR utilities out of the box.”

Obviously, I was looking for something more than your pedantry.

Re: Mithril.js 2.0 Released

#19

Post by wishinghand »

simplify wrote: post #8

Mithril is a true work of art. Rendering, routing, and XHR are all provided in a bundle under 10kb. All pure JavaScript with no compilation needed. Closure-style components that make React Hooks look wholly unnecessary. And the list goes on. So many correct decisions made, slowly and carefully, by a fantastic community that values discovering the right way to do things above all else.

Not sure what React hooks are other than maybe a replacement for Redux, but how does using closures help out?

Re: Mithril.js 2.0 Released

#20

Post by lhorie »

oceanghost wrote: post #9

Can someone explain what Mithril is and why I might want it? Not a troll.

It's a web framework, similar to React/Angular/Vue. It comes with router and xhr utilities (like Angular), but it's smaller and faster than React/Vue.

What makes it interesting is that it has a very pragmatic philosophy: if you have 10 mins to spare, going over the getting started guide will cover the majority of what is really needed to build a meaningful web app, which makes it ideal for devs who aren't interested in complicated webpack setups and just want to get stuff done (you can use it idiomatically from a plain HTML and a CDN, even).

People like Mithril because it's more "vanilla JS" than other frameworks.

Post reply on HN