4 ms·

I tried Elm in ~2018 and it was delightful. Ended up checking it out bc it was mentioned as 'prior art' in Redux's website. Didn't end up adopting bc everyone a

I tried Elm in ~2018 and it was delightful. Ended up checking it out bc it was mentioned as 'prior art' in Redux's website. Didn't end up adopting bc everyone around me thought I was crazy to use something so niche. It's the kind of thing that even if you don't end up using, you come out with lessons that make you a better programmer. Some that I remember: - The compiler was fast, it made me aware that you could have an iterative workflow like most dynamic languages but driven by types - The language/framework constructs (views, updates, etc) made it clear what kind of functionality had to live where so it makes me aware to define roles/arch in React apps that are 'just components' - Error messages are just awesome, it was the clearest I had seen at that point and made me realize other languages just haven't paid enough attention to make them more usable

ilikeorangutans 3y ago
Agree on all points. It's delightful to compile your app and... it just works. No nulls. I still use it for personal projects where 8 can but Elm is showing its age. Newer JavaScript APIs are not well supported and ports, while I understand why they exist, can be painful to use. But I'd still recommend it. Way more fun than any other fronted framework library I've used and the functional nature was a fun challenge for me.
- hombre_fatal 3y ago
  I still use Elm for personal projects as well. It’s nice to come back to an old project and become immediately productive not just because of the type system but because all Elm apps work the same. Coming back to an old React app is usually a pain because everything changes between projects, even the state management architecture.
_raul 3y ago
Exactly the same delightful experience here. Sadly it’s only become an even harder sell since then.
- cyberpunk 3y ago
  Every single place I've worked that adopted it has like one or two elm repos left where no one has had the time to rewrite it into ts yet, and there's maybe one developer who still understands it. I've not seen anyone picking it for new dev in... a really long time. Shame, really.
  - boxed 3y ago
    I use it at work. I tried to write Vue once and just hated it with a passion, so rewrote that part in Elm and was much happier.
busfahrer 3y ago
> It's the kind of thing that even if you don't end up using, you come out with lessons that make you a better programmer. Sort of a modern front-end developer's version of reading SICP even if you're not going to end up coding in Lisp, but because it makes you a better programmer, as you say. Interesting take!

ilikeorangutans 3y ago

Agree on all points. It's delightful to compile your app and... it just works. No nulls. I still use it for personal projects where 8 can but Elm is showing its age. Newer JavaScript APIs are not well supported and ports, while I understand why they exist, can be painful to use. But I'd still recommend it. Way more fun than any other fronted framework library I've used and the functional nature was a fun challenge for me.

hombre_fatal 3y ago
I still use Elm for personal projects as well. It’s nice to come back to an old project and become immediately productive not just because of the type system but because all Elm apps work the same. Coming back to an old React app is usually a pain because everything changes between projects, even the state management architecture.

_raul 3y ago

Exactly the same delightful experience here. Sadly it’s only become an even harder sell since then.

cyberpunk 3y ago
Every single place I've worked that adopted it has like one or two elm repos left where no one has had the time to rewrite it into ts yet, and there's maybe one developer who still understands it. I've not seen anyone picking it for new dev in... a really long time. Shame, really.
- boxed 3y ago
  I use it at work. I tried to write Vue once and just hated it with a passion, so rewrote that part in Elm and was much happier.

busfahrer 3y ago

> It's the kind of thing that even if you don't end up using, you come out with lessons that make you a better programmer. Sort of a modern front-end developer's version of reading SICP even if you're not going to end up coding in Lisp, but because it makes you a better programmer, as you say. Interesting take!