|
|
|
|
|
by sebringj
961 days ago
|
|
IMO Web Components generally suck in developer experience but are good for bridging different js projects or web frameworks as the web components are very compatible between js frameworks. You can literally make a thin wrapper to expose your js flavored framework-based component such as react for example and expose it as a web component to another system such as angular 1 for example and it will work pretty well. You could potentially use this strategy to have parallel tracks of development where you can create an entirely new framework from scratch and start to share that functionality in the legacy project while you're in the process of upgrading which could take a long long time in some cases. At least you won't be continually working on the old one and adding more tech debt... although one could argue this wrapper approach is tech debt. |
|