It depends, generally, I would say the guide for users is in encouraging patterns/providing utilities that avoid the issues. At the same time, if it can be solved in runtime, consistently, without introducing other special cases, or being too fragile, then maybe even if complicated could work.

Sounds good, I'm curious what's the issue with it, or what demonstrates?

pd: FOUC is Flash of unstyled content, not "Frame". I suppose a Flash could happen within many frames. 🤓

removing 11k LOC should be everyones goal

The force is strong, html6:
- strict parser, no autofixing html, back to xml?
- self-closing tags
- fix boolean attributes
- remove useless tags
- simplify web components api for sharing components between frameworks/js
- simplify dom apis

En lo posible pasar una noche en Cabo Polonio y rezar para que no esté nublado, porque de noche mirar al cielo te vuela la cabeza. De paso una empanadita de mejillones.

Thanks added it github.com/Devographics...

adorable, so cool to see it become a real item! quack! quack!

For future js/html surveys, could be possible to consider to always include a question on the lines of "are you required to write javascript-less forms/widgets?", and ask to clarify why so. Example: gov websites/accessibility, etc. I'm interested to see what people could say. Thanks!

The way I see it
- events do not collapse (firing events may put you in the initial state [no optimization])
- events do not model derivation, so may lead to have to do manual synchronization of state, which causes glitches (main incentive for using signals)

@ryansolid.bsky.social mentions in an article, something on the lines that **mutation** behaves or relates to events.

the comments deletions mess up my posting btw

Kind of uncalled-for all these comments
@webreflection.bsky.social

In any case, I'm referring to the fact that if you eval third party on your service worker that it will behave as if you were able to load it from anywhere, which is what you complain about.

Seems to me, you misunderstood.

your post shows code is being loaded from a third party, esm.run, so what I said applies,whatever. btw I was looking in Mdn and it seems possible to load service workers from other domains with some headers, but not sure, took a quick look

if the service worker you loaded from a third party gets hijacked, it could cache your whole page and while your server is fine users that already visited your page will see what the hijacked service worked wants

Websites are well known for going down or being taken over. If a hijacked SW loads from these, and caches malicious code forever... I wouldn't want to be in the position of asking customers to burst their cache via the official FB page… imagine it happens to a big website.. it would make the news