Learning Elm by porting a medium-sized web front end from React (2019)

Re:Learning Elm by porting a medium-sized web front end from... by marc136 on Thursday February 29, 2024 @06:07PM (#39556395)

For anyone new to Elm, please know that you have a stable language with no major changes since 2018 and no official release since end of 2019, see https://iselmdead.info and decide if that is a bad or a good thing for you.

And if you are thinking of starting now, you should not focus on what undocumented feature (or hack) was taken away in 2018 that allowed injecting arbitrary JavaScript code that easily broke all guarantees of the language https://discourse.elm-lang.org/t/native-code-in-0-19/826 but rather if Elm fits your current (and maybe future) needs. If it does not, keep looking for alternatives.

[ Parent | on HN ]

Re:Learning Elm by porting a medium-sized web front end from... by tasuki on Friday March 01, 2024 @02:28AM (#39559463)

The "no updates for past five years" is my favourite feature of Elm.

I have some five or so projects written in Elm and enjoy every time I don't have to upgrade them because no new version was released!

[ Parent | on HN ]

Re:Learning Elm by porting a medium-sized web front end from... by marc136 on Friday March 01, 2024 @04:52PM (#39567228)

That's high on my list, too.

The only fear I have is that I won't be able to install packages that no longer exist when I switching machines.

But by running

  ELM_HOME="$PWD/deps" elm make ...

I can get those downloaded into the directories and add them to the VCS.

[ Parent | on HN ]