@DannyEngelman This seems obvious for DOM manipulation in general within a FE framework, but web components just *feel* different, so it’s easy to lose sight of it.
A big learning from building Web Components for about 7 months now is that, if you think they might be used in frontend frameworks at all, you have to be very careful about messing with light DOM content. VDOMs are not aware of your messing around.
@DannyEngelman For example if a web component is passed a text node via its default slot, and, say removes that node for whatever reason, a FE framework will never be able to change that text content because the node it’s trying to update won’t exist anymore, but it won’t know.
_or_ they only learn engineering, get a job engineering, and then end up in an echo chamber where they neither learn anything new or think of anything new because all they knew was engineering-specific from the start.
Maybe biased but I think you have to find people that managed to find their way to engineering organically. People chase money and get burned out because they don’t actually enjoy it that much.
@StarbucksCare there was a piece of wood in my coffee and it broke my grinder. All I’m getting from yall is that I can take it back to the grocery store and get a refund, but that seems like not a lot for a piece of wood in the coffee and a busted grinder.
@Una I've been so JS heavy for the past few years, but I'm in a design system role now and I've been very conscious of all the CSS happening around me! Do you know if there's like a mega list of new features? Some of them sound so exciting.