|
|
|
|
|
by antouank
3247 days ago
|
|
I don't want to, but the "market" is forcing me. Being a contractor, I change teams and projects all the time. And most of the time when I join a team with an existing project, the devs that started it are pretty opinionated on everything. So sadly simple vanilla JS is not an option if you want to be a preferable candidate for projects.
Most of the teams prefer piling libraries upon libraries cause they think it will make things "convenient" or because it's the new exciting trendy library.
Whereas I've seen the opposite in the long-term, they make things more complicated and eventually impossible to maintain/reason with. I'm not trying to sell Elm to anyone, if you don't like it, don't use it.
But to me the advantages are quite obvious and I'd take it over any JS framework/library out there.
I just hope I could use it at work as well. There are only a few Elm jobs out there right now. |
|