That is unfortunately not true. The framework with the best marketing will win. That's why frameworks like angular and react are so popular. Both are designed to work well in large teams that work on huge codebases.…
v2.0 is coming. Breaking changes are minor stuff. Migration of my very large app took me about an hour. The API of mithril is pretty much settled, which IMO is a good thing. We even plan to remove stuff for next major.…
Have you tried mithril.js?
Problem with this approach is, that it only works for fairly simple stuff. Todays webapps have pretty complex UI with a lot of ramifications and complex dependencies of widgets. Such things are much easier to build if…
but a good one :D
It's a library for building webapps. Router and Ajax lib are a pretty obvious requirement for every webapp.
mithril.js includes a router and an ajax helper (that is much simpler than fetch) If you include those in preact they may have similar size.
That is unfortunately not true. The framework with the best marketing will win. That's why frameworks like angular and react are so popular. Both are designed to work well in large teams that work on huge codebases.…
v2.0 is coming. Breaking changes are minor stuff. Migration of my very large app took me about an hour. The API of mithril is pretty much settled, which IMO is a good thing. We even plan to remove stuff for next major.…
Have you tried mithril.js?
Problem with this approach is, that it only works for fairly simple stuff. Todays webapps have pretty complex UI with a lot of ramifications and complex dependencies of widgets. Such things are much easier to build if…
but a good one :D
It's a library for building webapps. Router and Ajax lib are a pretty obvious requirement for every webapp.
mithril.js includes a router and an ajax helper (that is much simpler than fetch) If you include those in preact they may have similar size.