News for hackers. Stuff that matters.
Re:SVGs as Elm Code by skybrian on Thursday November 03, 2022 @03:03PM (#33455782)
Elm is stagnant. There's been no release since October 2019. It's a problem because there are known bugs.

Elm is also unstable; there's no guarantee Evan won't break things in the next release.

It's a bad combination. A fork could in theory fix this. Has anyone done it, though?

Re:SVGs as Elm Code by aarpmcgee on Thursday November 03, 2022 @03:41PM (#33456353)
I am particularly interested in this project that transpiles to TypeScript: https://github.com/eeue56/derw
Re:SVGs as Elm Code by dhucerbin on Thursday November 03, 2022 @03:28PM (#33456146)
There is Gren, but I didn’t use it.

https://gren-lang.org/

Re:SVGs as Elm Code by cardanome on Thursday November 03, 2022 @03:59PM (#33456642)
> Elm is also unstable;

> no release since October 2019

Three years with literally not changes is pretty stable in the fronted world.

The known bugs are not a huge blocker for most people.

Even if a new version with breaking changes would arrive tomorrow you could still keep using the version of Elm that worked fine for years. Really no issue.

Re:SVGs as Elm Code by ollysb on Thursday November 03, 2022 @04:12PM (#33456809)
https://www.roc-lang.org/ looks very interesting, it's from Richard Feldman who's done a ton to promote Elm over the years and also happens to work at NoRedInk.
Re:SVGs as Elm Code by cardanome on Thursday November 03, 2022 @08:34PM (#33460104)
> quality-of-life improvements inspired by dynamic languages (always being able to run your program even if there are compile errors, automatic serialization and deserialization using schemas determined by type inference, reliable hot code loading that's always enabled and requires no configuration to set up, etc.)

They get it! Especially the being able to run your program even with compile errors part. Looking at you Golang and Zig with your unused variable errors. Let me do my prototyping!

And yeah, Richard Feldman is awesome. Roc is sure worth keeping an eye on.

Re:SVGs as Elm Code by 1-more on Thursday November 03, 2022 @04:28PM (#33457036)
> Elm is stagnant. There's been no release since October 2019. It's a problem because there are known bugs.

There are. I have never encountered them in my life but yeah there are. Fork it if they're really holding you back

> Elm is also unstable; there's no guarantee Evan won't break things in the next release.

I'm showing my privilege as someone who started with elm with 0.19 after all the big emergent patterns had emerged, but here goes: the FFI workaround that was broken from 18 to 19 was telegraphed for years. Earliest mention about it being disfavored I can find is from 2015 [1]. Conversely with 0.19.1 we get "If you like what you see now, that's pretty much what Elm is going to be for a while." [2] Ports and Custom elements make it such a non-issue to interact with JS while keeping your state in elm that it's just never held me back shrug.

> It's a bad combination. A fork could in theory fix this. Has anyone done it, though?

Gren, Derw, and eventually Roc compiled to JS/WASM could all do it I guess. Remains to be seen, but it's a very exciting space right now. It's a bit like The Velvet Underground: they only sold 20k records, but everyone who bought a copy started a band (or so the saying goes).

[1] https://groups.google.com/g/elm-dev/c/1JW6wknkDIo/m/H9ZnS71B... [2] https://github.com/elm/compiler/blob/master/roadmap.md

Re:SVGs as Elm Code by chillfox on Thursday November 03, 2022 @08:45PM (#33460192)
Nope, because anyone forking would have to come up with new name and run their own community.

If you are building an SPA then there is always Mint[1] (it's an Elm like language).

  [1]: https://github.com/mint-lang/mint