We have one Elm project at work, and frankly it is a nightmare because no one wants to take those tickets and everyone avoids it like it is radioactive. Personally I have had to do quite a few of them and every time I find it worse compared to React, people just seem to hate it and it is very difficult to find people who want to work with it, so that project is now being rewritten in, guess what, react.

I’ve had to deal with a nightmare Elm project. The difference is, I know what I’m doing. I solved all the problems, created examples to lead other devs and everything was fine. Have your company contact me if you need help.

i could say the exact same thing as a React dev.

> I’ve had to deal with a nightmare Elm project. The difference is, I know what I’m doing. I solved all the problems, created examples to lead other devs and everything was fine. Have your company contact me if you need help.

I’ve had to deal with a nightmare React project. The difference is, I know what I’m doing. I solved all the problems, created examples to lead other devs and everything was fine. Have your company contact me if you need help.

Frankly, I've worked with a couple React projects that are exactly like you describe, too.

The key difference being the team has 20 people that are fluent in React, vs the guy that decided to write it in Elm and left last year.

I've seen those React projects get rewritten.

Brooo look there is no state! Except that there is this massive state object being passed around!

I have experience from one Elm project at work and it is precisely like that, some massive state object that is passed around. No one wants to work with that project.