3 ms·
This post reminds me of these other two [0, 1] that ultimately lead Leo Horie to create Mithril [2], a tiny (5 KB down the line) but complete MVC framework that
by pygy_ 12y ago
This post reminds me of these other two [0, 1] that ultimately lead Leo Horie to create Mithril [2], a tiny (5 KB down the line) but complete MVC framework that also eschews most of the criticism raised by the OP.
The Mithril blog is also worth a look, it addresses a lot of concrete scenarios with recipies to solve common front end problems with the framework. For example, here's a post on asymetrical data binding [3].
————
0. http://lhorie.blogspot.fr/2013/09/things-that-suck-in-angularjs.html http://lhorie.blogspot.fr/2013/09/things-that-suck-in-angula...
1. http://lhorie.blogspot.fr/2013/10/things-that-suck-in-angularjs-follow-up.html http://lhorie.blogspot.fr/2013/10/things-that-suck-in-angula...
2. http://lhorie.github.io/mithril/ http://lhorie.github.io/mithril/
3. http://lhorie.github.io/mithril-blog/asymmetrical-data-bindings.html http://lhorie.github.io/mithril-blog/asymmetrical-data-bindi...
- kaonashi 12y agoThat framework has its own problems, like you have to wrap all your data structures into the mithril collections/models so that they can communicate with the views.
- pygy_ 12y ago> you have to wrap all your data structures into the mithril collections/models so that they can communicate with the views. Only when you need bidirectional bindings, and you're not forced to use the builtin `m.prop()` helpers, you can easily whip your own if they don't work for your use case. See my last link for an example.
- kaonashi 12y agoIsn't that the whole point though? I mean, discarding existing DOM with forms is a horrible experience.