Elm in Production: 25K Lines Later

Re:Elm in Production: 25K Lines Later by tomtheelder on Monday July 31, 2017 @11:11AM (#14892716)

I would disagree strongly with this, but I don't quite know how to put my objection into words. The enforced functional purity, "true" and incredibly friendly compiler, and the robust message system are all things that I don't think you really get in those other languages. To me, it's a bit like saying that you get all the benefits of Haskell in Java, because Java is also statically typed.

[ Parent | on HN ]

Re:Elm in Production: 25K Lines Later by jnbiche on Monday July 31, 2017 @11:25AM (#14892847)

Please read my comment again, I said "many if not most" of the benefits. And I was referring specifically to the tire system, not the language as a whole.

Listen, I love pure functional languages, but the step up from JavaScript to flow in program correctness is greater than the step up from flow to elm (in my opinion). Flow even has sum types.

Have you actually tried flow?

[ Parent | on HN ]

Re:Elm in Production: 25K Lines Later by simplify on Monday July 31, 2017 @01:19PM (#14893956)

I've tried to use flow three times now, but the tooling just isn't there yet. It might be better now, but Facebook doesn't seem to invest heavily in developer UX.

[ Parent | on HN ]

Re:Elm in Production: 25K Lines Later by jnbiche on Monday July 31, 2017 @01:39PM (#14894227)

What problem did you have?? I've been using Flow.js for work for several years now, to great success. I feel very uncomfortable now writing plain JS.

[ Parent | on HN ]

Re:Elm in Production: 25K Lines Later by simplify on Monday July 31, 2017 @02:59PM (#14894925)

For some reason I could never get flow's in-editor errors and type information to work. Personally I use TypeScript. Their sublime support is nice and fast.

[ Parent | on HN ]