I think I learned Elm for all the same reasons you listed.
Also am just tired of maintaining giant react apps that are slow and full of bugs.
Trying to evangelize Elm at work as much as possible these days in hopes of writing Elm full-time
How do you go about it?
Making short presentations with demos, benefits/advantages over React. Sharing my blog posts about it, and overall just talking about it with coworkers
Nice.
Is there a part of the app that you're working on that's been a constant source of bugs?
Maybe you can rewrite it in Elm to make an even stronger case for using it.
I like the approach Evan recommends here.
... it is important to be strategic in choosing your first project. Do not just write Elm code because you like it. Fix a problem.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
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 I learned Elm for all the same reasons you listed.
Also am just tired of maintaining giant react apps that are slow and full of bugs.
Trying to evangelize Elm at work as much as possible these days in hopes of writing Elm full-time
How do you go about it?
Making short presentations with demos, benefits/advantages over React. Sharing my blog posts about it, and overall just talking about it with coworkers
Nice.
Is there a part of the app that you're working on that's been a constant source of bugs?
Maybe you can rewrite it in Elm to make an even stronger case for using it.
I like the approach Evan recommends here.