Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

benhoyt.com

Post reply on HN
Print view View original

1–10 of 95 posts

Re: Learning Elm by porting a medium-sized web frontend from React (2019)

#2

Post by jrvarela56 »

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

Re: Learning Elm by porting a medium-sized web frontend from React (2019)

#3

Post by ilikeorangutans »

jrvarela56 wrote: post #2

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…

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.

Re: Learning Elm by porting a medium-sized web frontend from React (2019)

#5

Post by _raul »

jrvarela56 wrote: post #2

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…

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

Re: Learning Elm by porting a medium-sized web frontend from React (2019)

#6

Post by busfahrer »

jrvarela56 wrote: post #2

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…

> 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!

Re: Learning Elm by porting a medium-sized web frontend from React (2019)

#7

Post by hombre_fatal »

ilikeorangutans wrote: post #3
jrvarela56 wrote: post #2

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…

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 fo…

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.

Re: Learning Elm by porting a medium-sized web frontend from React (2019)

#10

Post by roebk »

datadeft wrote: post #8

The website tells the full story: https://elm-lang.org/ © 2012-2021 Evan Czaplicki

What story does that tell?

React's would say 2022 - https://github.com/facebook/react/releases

There's engineering effort happening behind the scenes on both projects, the releases have slowed, and big changes are coming to both Elm and React.

Post reply on HN