3 ms·
TL;DR: they bridged Elm with React, and when they started using Web Components there was an impedance mismatch between the bridges between Elm/React and WebComp
by cwzwarich 4y ago
TL;DR: they bridged Elm with React, and when they started using Web Components there was an impedance mismatch between the bridges between Elm/React and WebComponents and the bridge between Elm and React, so they had to pick one of Elm and React.
- savanaly 4y agoI would say the Web Components portion of this article is a detour, mainly he was explaining his discovery you can't utilize web components to marry React and Elm together as one would hope. The real TLDR is it's too hard to hire Elm devs.
- zackbloom 4y agoI wonder how you got that TLDR. He literally said they hired a bunch of people only because they did Elm.
- macintux 4y agoThat's a bit too short, I think. TypeScript plays a role as well, as does an acquisition. I liked the description of the internal discussions. Working at a larger company where decisions are made in a completely different part of the organization and you're stuck dealing with the ramifications leaves me a little nostalgic for a smaller firm where it's practical to engage all stakeholders.
- jrumbut 4y agoOn the other hand, at this larger organization it was possible to have devs devote months to experiments that were ultimately shelved. It was kind of cool that they really explored all the avenues for making it work.
- Herval_freire 4y agoThey had an acquisition where the code became 75% react over night due to the acquisition. This was the major turning point. Purely business, purely popularity. It wasn't technical superiority.
- jdlshore 4y agoNo, they didn’t end up using WebComponents. The real issue was that it was too much trouble to have Elm & React in the same codebase. They were migrating the code to Elm, but then merged with another company. Now 75% of their company was only familiar with React. Only 6 people were strong Elm advocates. Because React and TypeScript had progressed since they first decided to use Elm, because the cost of maintaining two frameworks was high, and because the cost to switch to Elm was out of reach, they decided to “contain” Elm by no longer permitting it for new components.
- benatkin 4y agoIt also didn't impress them. I don't like the idea of using Web Components with Stencil either. I like Web Components though.