-
seanpltr Thanks for checking in! As of now we’re still enjoying Elm and Elixir where we’re already using it, but we’re no longer choosing it for new things. (1/2)Permalink On twitter.com
Mood +3 🙂
-
seanpltr Our Ruby and TypeScript/React teams and codebases have outgrown our Elixir and Elm ones, in part due to an acquisition we made at the start of 2019, and we’re at the point where we need to bet on the things most of our engineers are already using. (2/2)Permalink On twitter.com
-
seanpltr This is a story I feel like we need to tell publicly; it’s just not quite as entertaining and exciting as the “look, new toys!” story of my previous talks.Permalink On twitter.com
-
seanpltr If I were starting something from scratch today, I’d still consider Elm/Phoenix an attractive option, as long as you were investing in building the parts of the ecosystem you found missing to reap the benefits of robustness and scalability.On twitter.com