Re: [w3c/webcomponents] [idea] Allow custom element naming on a per-shadow-root basis. (#488)

The standards process is much slower than necrobumping this thread, so it seems fine if we are to continue to grow ideas.

If you don't see the power that comes with Vue/React/Angular/etc on component-scoped naming of components, then there's not much else I can tell you other than you should learn more about those libraries.

All I have proposed here was to have a way to scope element names on a per-shadow-root basis, and it doesn't matter if it was v0 or v1 when I started the discussion, the same concept still applies:

Sclabale component architecture nowadays *always includes* per-component naming of inner components, and it would be great to have this in Web Components just like we have it in basically every other web framework.

Whoever thought making Custom Elements all globals is simply thinking in globally-polluting sort of way, and now we will all have to pay for it in the long run. The future generations of web developers will have yet another way to ridicule the web and will continue to make triple A titles outside of web technology unless we make serious design decisions that are based on modern engineering standards (f.e. not polluting globals).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/488#issuecomment-341767707