4 ms·
I think it is newsworthy because it details the strengths and weaknesses of Elm in what looks like a fairly complex project. I already use and like Elm better
by innocentoldguy 8y ago
I think it is newsworthy because it details the strengths and weaknesses of Elm in what looks like a fairly complex project. I already use and like Elm better than any other front-end framework, but if I was considering Elm as a possibility, this information would be quite useful, I think.
Definitely not the most important thing on the list, but I use Vim to code so IDE integrations mean absolutely nothing to me. I hate IDEs. To companies and teams that can't go to the bathroom without an IDE, that may be a deal breaker. Either way, it is good information to have.
- quickthrower2 8y agoJust so you know, Vim has Elm plugins: https://github.com/ElmCast/elm-vim https://github.com/ElmCast/elm-vim. As an aside, of all the things I judge a job offer on, whether or not they use IDEs is pretty far down the list. I can get Visual Studio to behave like VIM and vice versa probably. I find it interesting that people sometimes hold this in high regard.
- cttet 8y agoOne of the reason I like Elm is that it has great potential for great IDEs. If you use Vim with lot of plugins then it is already sort of a minimal IDE right? Most IDE you hate perhaps have a lot of UX design problems. Good IDEs should aim for a better overall coding experience, by this definition. For example in Elm, all the nice error messages can appear next to the line, and all the case-of statements can be auto-completed according to the type definition, it all adds to an overall better coding experience.