I will listen to the podcast soon (already downloaded), but I have already read the blog post about the decision to retire Elm at Culture Amp: On Endings: Why & How We Retired Elm at Culture Amp
In short, React wins again because of its unique advantage: everyone uses it
That’s a bit of irony because a guy from the React core team recently tweeted (I can’t find the tweet back) that if you want a full React experience you should use ReScript, a functional language based on OCaml. Not that different from Elm…
What’s the irony here? Because from my perspective Rescript is very different from Elm. And those differences enable Rescript to embrace React style of building applications but limits Elm in doing so.
I finally finished listening to this. It was a great episode. I was surprised by how much I missed listening to Kevin Yank’s voice. I’m looking forward to more episodes of Elm Town though, even sans Yank.
Even though I read the accompanying blog post, I’m glad y’all made this podcast episode, for some reason it all helped me understand things better.
There were a lot of similarities between Culture Amp and what I’m working on but after listening to podcast episode I see there are interesting difference that make Culture Amp’s decision to leave Elm make more sense.
Also… not to Monday morning QB what went down. But it was interesting how the experiment Culture Amp ran with web components was to make the most complicated web component they had. Which makes sense… as general rule. However what I’ve learned, is that when making web components that are designed to be shared with Elm and something else (I haven’t tried this with React). What works best is keeping things simple and composable And when I say “simple”, it’s not that the web component can’t do anything interesting or complex. It’s that the API for the web component needs to stay simple. Most of the time this means, it’s going to be simple “inside and out” but not always. When you can encapsulate something in a web component that has a simple API but is doing something complicated that’s web components at their best.