4 ms·
No, 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 co
by jdlshore 4y ago
No, 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.