Mithril's omission is telling, as it it often faster than even Elm by 50% or so.
http://lhorie.github.io/todomvc-perf-comparison/todomvc-benc...
Blazing Fast HTML: Elm vs. React vs. Angular vs. Ember
11–20 of 55 posts
Re: Blazing Fast HTML: Elm vs. React vs. Angular vs. Ember
#12They should really spend more time on making the docs less attrocius for Elm. That's more important than benchmarks.
(Coming from someone who appreciates Elm)
Re: Blazing Fast HTML: Elm vs. React vs. Angular vs. Ember
#13Whats the difference between a few seconds of loading time for a site that only needs to load its bundle once? Sure its nice for it be faster but the main benefit I thought is you don't need to reload pages as you navigate.
This benchmark has nothing to do with page load time.
It's about rendering time, when everything is already loaded.
Re: Blazing Fast HTML: Elm vs. React vs. Angular vs. Ember
#14Oh no...benchmarks.
Honestly, your decision to use any of the frameworks in the article should not be based on a benchmark. The frameworks here differ so much in how they work, the mental thought process you use in them, etc.
What is the technical debt of Elm? Training for developers to learn something other than JS, etc. This is a much bigger factor in a framework decision than a benchmark. Especially when all of them are fast and only a few cases would you even notice a difference between them.
Please, don't use this to decide which front-end framework to use. Nor switch from one you are using, "just because it's faster!". Save yourself and your co-workers the headache.
Re: Blazing Fast HTML: Elm vs. React vs. Angular vs. Ember
#15Mithril's omission is telling, as it it often faster than even Elm by 50% or so. http://lhorie.github.io/todomvc-perf-comparison/todomvc-benc...
1. That benchmark is rather outdated - React 0.10, Angular 1.2.14 ...
2. Article seems to compare most popular frameworks, so no surprise Mithril didn't make it since more popular frameworks like Vue are also not on the list
Re: Blazing Fast HTML: Elm vs. React vs. Angular vs. Ember
#16Whats the difference between a few seconds of loading time for a site that only needs to load its bundle once? Sure its nice for it be faster but the main benefit I thought is you don't need to reload pages as you navigate.
Possibly misunderstood the article, but it seems they are comparing performance once the bundle is already loaded. That said, as someone who personally prefers using browser over apps ( at least for content consumption, rather than something like a password manager) it is nice to have things boot up quickly.
Re: Blazing Fast HTML: Elm vs. React vs. Angular vs. Ember
#17Oh no...benchmarks. Honestly, your decision to use any of the frameworks in the article should not be based on a benchmark. The frameworks here differ so much in how they work, the mental thought process you use in them, etc. What is the technical debt of Elm? Training for developers to learn something other than JS, etc. This is a much bigger factor in a framework decision than a benchmark. Especially when all of th…
Those are sensible questions!
Here is more info about one company's experience with Elm when it comes to technical debt, training developers to learn something other than JS, etc:
Re: Blazing Fast HTML: Elm vs. React vs. Angular vs. Ember
#18I believe the saying is "Lies, damn lies and benchmarks".
That said, he does make a case that elm is competitive with other frameworks, which is all anyone should take from a language benchmark, in my opinion.
Re: Blazing Fast HTML: Elm vs. React vs. Angular vs. Ember
#19No vue.js?
Re: Blazing Fast HTML: Elm vs. React vs. Angular vs. Ember
#20For the love of * (pick your preferred deity, I'm going with Flying Spaghetti Monster), stop benchmarking on ridiculously simple TodoMVC apps.
They are not at all representative of the complexity costs that emerge from real apps, which often mitigate differences between frameworks considerably.
(Apart from the fact that creators benchmarking their own framework know how to optimize it best).