I have seen React apps, and it is pushing towards frontend Monolithic with confused client and server side rendring. Web components provide huge power, speed, and open architecture, which makes it a future candidate of Micro frontend.
Whenever I hear that web components are lacking or pointless if there are frameworks like React, it blows my mind. Web development isn't limitied to throwing all kinds of heavy libraries on your own platform: We're building content that can be used as ads or included as regular imteractive content anywhere on any website, so we're limited in which and how many ressources we can use. Because web component are native and don't require a backend or a heavy library or compiled JS, they're often the best solution to include our pieces without causing any conflicts on a website (we might not even know on which websites our service will be used).
Agree, but if you're talking about ads, let's be honest. All the bots, trackers, heatmaps, cookie consents, oauths and ad scripts are much heavier than frontend framework loaded into the browser, that weights maybe 200 kb
how is it going so far? I see these WC frameworks like Lit and WebC bridging the gap but doesn't that defeat the purpose of moving away from all these frameworks?
@@MarkVolkmann either you are wrong or ChatGPT is wrong. It states you can and gives the code. Too busy with another project to verify, but I think functions likely work
Interesting. Thanks for reminding me about these. For my current app I need all the performance bonuses I can get, so the gains there would be the main draw card. My other considerations would be a solid UI library, a thriving community, and some sort of store (like vuex).
Web components, are very well suited to migrate legacy projects as they allow incremental migration of the UI. With React, this would be much harder to achieve
Very clear explaination and clear separation of API's that web components based on. Although I have already written some web components, I had not thought before that these are different APIs. In this respect, it is a very valuable video for me, thank you.
I have seen React apps, and it is pushing towards frontend Monolithic with confused client and server side rendring. Web components provide huge power, speed, and open architecture, which makes it a future candidate of Micro frontend.
Whenever I hear that web components are lacking or pointless if there are frameworks like React, it blows my mind. Web development isn't limitied to throwing all kinds of heavy libraries on your own platform: We're building content that can be used as ads or included as regular imteractive content anywhere on any website, so we're limited in which and how many ressources we can use. Because web component are native and don't require a backend or a heavy library or compiled JS, they're often the best solution to include our pieces without causing any conflicts on a website (we might not even know on which websites our service will be used).
Agree, but if you're talking about ads, let's be honest. All the bots, trackers, heatmaps, cookie consents, oauths and ad scripts are much heavier than frontend framework loaded into the browser, that weights maybe 200 kb
The last two fairly big commercial projects I worked on asked me to switch their existing code base to Web Components. So it's probably the latter.
how is it going so far? I see these WC frameworks like Lit and WebC bridging the gap but doesn't that defeat the purpose of moving away from all these frameworks?
Can we use functions rather than classes for creating custom elements? I'm not a huge fan of classes.
No. Web components must be defined by a class.
@@MarkVolkmann either you are wrong or ChatGPT is wrong. It states you can and gives the code. Too busy with another project to verify, but I think functions likely work
No, you can use functional style wrappers like atomico or solid-element but they will be creating a class for you anyway :)
Interesting. Thanks for reminding me about these. For my current app I need all the performance bonuses I can get, so the gains there would be the main draw card. My other considerations would be a solid UI library, a thriving community, and some sort of store (like vuex).
Nice video. Learned lots of new things. Thank you.
Web components, are very well suited to migrate legacy projects as they allow incremental migration of the UI. With React, this would be much harder to achieve
Just getting started, if you ask me. I’m starting a project with them as we speak
Very clear explaination and clear separation of API's that web components based on. Although I have already written some web components, I had not thought before that these are different APIs. In this respect, it is a very valuable video for me, thank you.