I think popularity is one measure of success, but by no means the only one and not necessarily even the most important. For example if I release a product to a small market, and nearly everyone in that market uses it, but in general nobody has heard of it... is that product still not successful?
In Elm's case, it is currently in a limited market. Very few webdevs seem to want to use anything other than component-based frameworks. The influx of new webdevs learn Javascript and naturally transition to one of those. Because it is the vast majority of what they find guidance for. And when something is new to you, you don't want to try something on the fringes and risk it fading into dereliction.
It usually takes a long term project to expose the weaknesses in a particular framework. Anyone can make something neat, live with it for a short while, and make a blog post about how awesome it is... long before they start to get worn out on the maintenance burden from accidental complexity. And when you can find literally hundreds of such posts, how could you believe differently until experiencing the bad parts first hand?
I use Elm. I consider it a really good platform. I recommend it all the time. Any product has some issues, but overall it is the best front end dev experience I've had so far. My users love it too, because we can generally repro and fix things quickly. (As yet, we don't keep bugs on our backlog for more than 1 sprint on our Elm projects. We don't get a lot of them reported, and when we do they are frequently fixed and deployed same day.)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think popularity is one measure of success, but by no means the only one and not necessarily even the most important. For example if I release a product to a small market, and nearly everyone in that market uses it, but in general nobody has heard of it... is that product still not successful?
In Elm's case, it is currently in a limited market. Very few webdevs seem to want to use anything other than component-based frameworks. The influx of new webdevs learn Javascript and naturally transition to one of those. Because it is the vast majority of what they find guidance for. And when something is new to you, you don't want to try something on the fringes and risk it fading into dereliction.
It usually takes a long term project to expose the weaknesses in a particular framework. Anyone can make something neat, live with it for a short while, and make a blog post about how awesome it is... long before they start to get worn out on the maintenance burden from accidental complexity. And when you can find literally hundreds of such posts, how could you believe differently until experiencing the bad parts first hand?
I use Elm. I consider it a really good platform. I recommend it all the time. Any product has some issues, but overall it is the best front end dev experience I've had so far. My users love it too, because we can generally repro and fix things quickly. (As yet, we don't keep bugs on our backlog for more than 1 sprint on our Elm projects. We don't get a lot of them reported, and when we do they are frequently fixed and deployed same day.)