3 ms·

Oh 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

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

rtfeldman 10y ago
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: https://www.youtube.com/watch?v=R2FtMbb-nLs https://www.youtube.com/watch?v=R2FtMbb-nLs
agentgt 10y ago
I very rarely see technology choice decisions based on performance. It probably should happen more often then it does. If anything most choices are based on popularity. Benchmarks are not the best way to advertise languages but regardless Elm has do well on so many fronts to make it competitive otherwise it will die to the popular frameworks/languages (usually the lowest common denominator). > 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. I would hope and fairly optimistic that people make decisions on a variety of compelling reasons (particularly tech people). Some of those reasons often can be performance. What you mean is don't make this the sole reason and even this "tip" isn't really helpful advice.
- Bahamut 10y ago
  There is one benefit of choosing based on popularity - it becomes easier to hire for, and more likely to find engineers enthusiastic about the work. In addition, it increases the number of eyes on it, which can surface difficult bugs/edge cases to get addressed.
  - agentgt 10y ago
    > There is one benefit of choosing based on popularity - it becomes easier to hire for, and more likely to find engineers enthusiastic about the work. In addition, it increases the number of eyes on it, which can surface difficult bugs/edge cases to get addressed. I didn't mean to sound like it isn't a good idea to have a good portion of your reasoning based on popularity. I have done it myself :) . But if your trying to make your framework popular you have to do some advertising (hopefully somewhat honest). I don't blame the Elm devs for publishing some benchmarks particularly when it is some impressive work they have done.

rtfeldman 10y ago

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: https://www.youtube.com/watch?v=R2FtMbb-nLs https://www.youtube.com/watch?v=R2FtMbb-nLs

agentgt 10y ago

I very rarely see technology choice decisions based on performance. It probably should happen more often then it does. If anything most choices are based on popularity. Benchmarks are not the best way to advertise languages but regardless Elm has do well on so many fronts to make it competitive otherwise it will die to the popular frameworks/languages (usually the lowest common denominator). > 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. I would hope and fairly optimistic that people make decisions on a variety of compelling reasons (particularly tech people). Some of those reasons often can be performance. What you mean is don't make this the sole reason and even this "tip" isn't really helpful advice.

Bahamut 10y ago
There is one benefit of choosing based on popularity - it becomes easier to hire for, and more likely to find engineers enthusiastic about the work. In addition, it increases the number of eyes on it, which can surface difficult bugs/edge cases to get addressed.
- agentgt 10y ago
  > There is one benefit of choosing based on popularity - it becomes easier to hire for, and more likely to find engineers enthusiastic about the work. In addition, it increases the number of eyes on it, which can surface difficult bugs/edge cases to get addressed. I didn't mean to sound like it isn't a good idea to have a good portion of your reasoning based on popularity. I have done it myself :) . But if your trying to make your framework popular you have to do some advertising (hopefully somewhat honest). I don't blame the Elm devs for publishing some benchmarks particularly when it is some impressive work they have done.