I agree a lot with this post, but there's one key aspect of the framework that ends the usage for me: The HTML written as functions aspect.
Sure, I can easily figure out the brain mapping between native HTML markup and the Elm HTML function syntax, but the majority of front-end developers (CSS and markup-focused folks) will stop dead in their tracks looking at The Elm Way.
I rarely work solo on projects anymore, and tend to have someone else handle the CSS and markup pieces to save time. Using Elm blocks the majority of folks I can now work with.
So, "making developers happy" with Elm rings true for "full stack" people, but I think the happy part ends for anyone that doesn't want to learn a new HTML syntax for no good reason (from their perspective).
Sure, I can easily figure out the brain mapping between native HTML markup and the Elm HTML function syntax, but the majority of front-end developers (CSS and markup-focused folks) will stop dead in their tracks looking at The Elm Way.
I rarely work solo on projects anymore, and tend to have someone else handle the CSS and markup pieces to save time. Using Elm blocks the majority of folks I can now work with.
So, "making developers happy" with Elm rings true for "full stack" people, but I think the happy part ends for anyone that doesn't want to learn a new HTML syntax for no good reason (from their perspective).