3 ms·
Mithril has a detailed “why this instead of react/vue/etc” article https://mithril.js.org/framework-comparison.html https://mithril.js.org/framework-comparison.
by kennywinker 5y ago
Mithril has a detailed “why this instead of react/vue/etc” article https://mithril.js.org/framework-comparison.html https://mithril.js.org/framework-comparison.html that I think should be mandatory for any library entering a crowded space like this. If only because i want to know the priorities of the developers.
- montroser 5y agoThat would be nice, but also we observers are not owed any such explanation by the creator.
- kennywinker 5y agoNo, but communities can set expectations, and then someone can choose to meet or buck the expectations of the community at their own risk. A good example of this is the TodoMVC convention. Instead of making "whatever demo app you choose" a convention developed to make a Todo app, so that people could compare frameworks in a more "apples-to-apples" way. A new framework with a Todo demo would likely get more traction than a framework with a Calendar demo, because it's easier to evaluate and understand how it works.
- scns 5y agoAnother would be the "Real World" example apps: https://codebase.show/projects/realworld https://codebase.show/projects/realworld https://github.com/gothinkster/realworld https://github.com/gothinkster/realworld