What is your experience so far?
How do you cope with basically not having deeply nested components?
Ask HN: Anyone Using Elm in Production?
1–10 of 74 posts
Re: Ask HN: Anyone Using Elm in Production?
#2Yes. The deeply nested components thing isn’t an issue at all. You build “components” as stateless views. It’s fundamentally the same as building an application out of all stateless components in redux.
Your model (the central state) becomes larger and more complex, but the size of your update function doesn’t expand as much as you’d think.
Meanwhile, the benefits from type-safety, pure functions, and extremely well-designed libraries like elm/parser & elm-UI are really terrific.
Re: Ask HN: Anyone Using Elm in Production?
#3What exactly does elm offer?
Re: Ask HN: Anyone Using Elm in Production?
#4I don't use it myself, but I was recently at Oslo Elm Day, where a consultant at The Norwegian State Railways shared his experiences with it (which were mostly good): https://youtu.be/yE9PKFI19RM
Re: Ask HN: Anyone Using Elm in Production?
#5If your question is whether Elm is mature enough for production, the answer is yes. There are some companies out there, but don't let their opinion condition your experience.
Rather than relying on other people's opinion a better experience for you would be to port one sub-component of your existing system to elm and see how it goes from there, while you gain trust and experience in the new system.
Re: Ask HN: Anyone Using Elm in Production?
#6What exactly does elm offer?
No run-time exceptions: https://elm-lang.org/blog/compilers-as-assistants
Re: Ask HN: Anyone Using Elm in Production?
#7I'm curious what Elm offers that cannot be done in TypeScript.
Re: Ask HN: Anyone Using Elm in Production?
#8What exactly does elm offer?
A strictly typed pure functional language that generates JavaScript. That, along with a clever compiler, makes them claim that apps built with Elm don't have runtime exceptions.
Re: Ask HN: Anyone Using Elm in Production?
#9I'm curious what Elm offers that cannot be done in TypeScript.
Much stronger type guarantees. TypeScript's strength and weakness is how it fits JavaScript like a glove. Elm is a different language entirely, so it can provide much better soundness. It's also a simpler language than JS / TS. TypeScript, being a superset of JS, has a lot of baggage. Elm is pretty small and conceptually simple. Elm is also a framework, not just a language, so it guides your team into building things in one, consistent way (for better or for worse). Finally, the Elm compiler is very good. It produces small, fast build artifacts. Compare the bundle sizes of Elm with the other competing frameworks here[0].
Re: Ask HN: Anyone Using Elm in Production?
#10Yes. The deeply nested components thing isn’t an issue at all. You build “components” as stateless views. It’s fundamentally the same as building an application out of all stateless components in redux. Your model (the central state) becomes larger and more complex, but the size of your update function doesn’t expand as much as you’d think. Meanwhile, the benefits from type-safety, pure functions, and extremely well-…
What is meant by "deeply nested components" and why can't you do them in Elm?