News for hackers. Stuff that matters.
Re:Why I Use Elm in 2023 by nequo on Tuesday May 23, 2023 @10:24AM (#36044790)
Have there been any efforts to fork it?

0.19 also prohibited interaction with non-Elm code which I recall a controversy about. But can't seem to find out if anyone forked 0.18 because of that.

Re:Why I Use Elm in 2023 by truculent on Tuesday May 23, 2023 @10:27AM (#36044824)
Not quite a fork, but Gren is a descendent: https://gren-lang.org/news/220530_first_release/
Re:Why I Use Elm in 2023 by 1-more on Tuesday May 23, 2023 @11:39AM (#36045895)
Gren is a fork. Their first commit is the head of Elm 0.19.1 right?
Re:Why I Use Elm in 2023 by giraffe_lady on Tuesday May 23, 2023 @12:02PM (#36046269)
The faq in the book says this about it:

> Gren started as a fork of Elm. This is mostly considered to be an implementation detail, a way to speed up initial development.

> It's not a goal of Gren to replace, or stay compatible in any way with, Elm.

A little vague but I read it as they're planning on diverging strongly and immediately with a clean break. Which doesn't make it not a fork I guess, but isn't what I normally think of when someone says a project is a fork of another.

Re:Why I Use Elm in 2023 by 1-more on Tuesday May 23, 2023 @12:35PM (#36046745)
Yeah I guess "stay compatible with" and "cover the same use cases" are the connotations for a fork and it really doesn't hit those, fair enough.
Re:Why I Use Elm in 2023 by cies on Tuesday May 23, 2023 @04:31PM (#36050466)
Fork means "to the originating project's source code and develop it further in the context and governance of a new project" in my understanding.

So Gren is a fork.

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)
Re:Why I Use Elm in 2023 by 1-more on Tuesday May 23, 2023 @04:35PM (#36050502)
It's such an easy restriction to work around that it just doesn't come up a ton on code that's always been written for 0.19. I imagine it was a monstrous hassle if you depended on it with a big 0.18 codebase, but the new JS interop (ports but more importantly custom elements) are very nice to work with tbh.

There's a third inspired-by-elm language Derw (after Gren and Roc that are mentioned elsefork) but I don't know much about it.