News for hackers. Stuff that matters.
Re:Why I Use Elm in 2023 by Nezteb on Tuesday May 23, 2023 @10:39AM (#36044984)
I don't think it's a fork, but prominent Elm developer/author Richard Feldman has been working with and hyping up Roc: https://www.roc-lang.org
Re:Why I Use Elm in 2023 by 1-more on Tuesday May 23, 2023 @04:26PM (#36050398)
He in fact works on Roc full time now! As does one other Roc contributor whose name escapes me. Exciting times.
Re:Why I Use Elm in 2023 by davidatbu on Tuesday May 23, 2023 @06:55PM (#36051879)
It is my understanding that roc aims to "bring Elm to the backend", so it does not at all look like a substitute for Elm.
Re:Why I Use Elm in 2023 by Nezteb on Wednesday May 24, 2023 @02:38AM (#36054833)
* * *
Re:Why I Use Elm in 2023 by davidatbu on Wednesday May 24, 2023 @04:34AM (#36055469)
From what I know from skimming the docs and listening to Richard's podcast, their focus currently is on achieving great compiled performance. Plus, from what I can tell, Richard is still a fan of Elm, so I'd guess he thinks there's space for Roc to contribute to the frontend (that last part is pure speculation though).
Re:Why I Use Elm in 2023 by davidatbu on Wednesday May 24, 2023 @01:07PM (#36061088)
Meant to say "... there isn't space ..."
Re:Why I Use Elm in 2023 by evntdrvn on Sunday May 28, 2023 @12:25PM (#36105464)
Interesting! From a surface language level it feels a lot like F#, but with purity and a managed effects system--which is something that I've kinda wished for/had to build patterns for in F# codebases... I'll have to keep an eye on it, thanks! (reading through the FAQ, there are some interesting design decisions! I appreciate the pragmatic focus. Didn't realize that it was non-curried lang until the FAQ)