Live data from Hacker News

A nice app on Elm street

madewithlove.be

41–50 of 84 posts

Re: A nice app on Elm street

#41

If I have time off to learn a new language in order to get a new Job, would Elm be a good choice? I wonder if picking a niche language would give me an advantage or there would be too few jobs.

The biggest problem with elm in production right now is that there is no backward compatibility yet (version < 1.0). Code written in Elm 0.18 is not compatible with code written in Elm 0.19.

Re: A nice app on Elm street

#42
post #31
post #29

Earlier quoted context omitted.

T.b.h. this is the reason why I will probably stay messing around with either PureScript or ReasonML but stay away from Elm.

Why exactly? Elm 0.19 is out on August 2018, and the only thing that's expected is 0.19.1 which barely changes anything (doesn't break any api). Seems like 0.19 is quite settled at this point.

Will my Elm code written today still be maintainable with an up-to-date elm environment in 3 years? It certainly isn't the case with code written 3 years ago.

Re: A nice app on Elm street

#43

For anyone new trying to get into Elm (as a language/tool), I would look elsewhere. ReasonML, PureScript, TypeScipt, etc are all better featured solutions. Having said that, the article is well written and thorough for anyone wanting to take a look into Elm. But there are massive problems with Elm itself which make it impossible to consider seriously. I have and still do use Elm in production, and went through the ni…

> Evan holds the naive view that everything can be rewritten in pure Elm and there's no reason not to. An overwhelmingly common use-case is 3rd party services or tracking libraries where it's impossible to re-implement; these apparently don't exist. He quite loudly holds the opposite view: instead of thinking you need to port everything to Elm (very common urge for newcomers), keep it in JS and use it over a port.

All the wording in https://discourse.elm-lang.org/t/native-code-in-0-19/826 seems to indicate the opposite. I'm not saying jQuery bindings are a good idea, but saying no to _everything_ b/c you don't want jQuery bindings is.

Re: A nice app on Elm street

#44
I like Elm as a language, but the community is extremely toxic, and it's not production-ready yet (version < 1.0, one-person project). Too bad, because it's a great project.

Re: A nice app on Elm street

#45
post #44

I like Elm as a language, but the community is extremely toxic, and it's not production-ready yet (version < 1.0, one-person project). Too bad, because it's a great project.

How is it toxic? All the comms I've read from Evan were pretty polite.

Re: A nice app on Elm street

#46
post #44

I like Elm as a language, but the community is extremely toxic, and it's not production-ready yet (version < 1.0, one-person project). Too bad, because it's a great project.

can you site some sources for the “extremely toxic” community? genuinely curious

Re: A nice app on Elm street

#47
post #44

I like Elm as a language, but the community is extremely toxic, and it's not production-ready yet (version < 1.0, one-person project). Too bad, because it's a great project.

> not production ready (version This is FUD. Elm is being used pretty successfully in production.

Re: A nice app on Elm street

#48

I am a back-end developer, and I don't know front-end. I also know very little of functional programming. Elm is the only language that I like writing, and where I don't feel in a state of frustration when I write. It might have a lot of limitations, bu tit makes me happy. Given that our job is basically to be in a constant state of half broken code, this makes me a huge fan of the language.

    our job is basically to be in a constant state of half broken code
In my experience, Elm code is only ever in a state of "horribly broken, won't compile" or "works". Whether that's a bug or a feature depends on what I'm trying to do...

Re: A nice app on Elm street

#49
post #35
post #29

Earlier quoted context omitted.

T.b.h. this is the reason why I will probably stay messing around with either PureScript or ReasonML but stay away from Elm.

Yeah, I balked at changing my apps to be 0.19 compatible. Now I'm kind of just "getting along" with 0.18 until I can do more of my front end work in Phoenix LiveView.

We have a 100 kloc Elm application and the upgrade process was quick. Tracking Elm releases is considerably easier than the JavaScript ecosystem.

Re: A nice app on Elm street

#50
post #44

I like Elm as a language, but the community is extremely toxic, and it's not production-ready yet (version < 1.0, one-person project). Too bad, because it's a great project.

Many companies rely on Elm now it’s definitely production ready.
Post reply on HN