Re: [csswg-drafts] [css-shadow-parts] consider putting more power on user instead of author

> So basically, the only proper solution here (when you work in a company vs indie projects) is to avoid shadow dom components or only to use the extremely reliable ones. It's sad because shadow elements are really great except for the impossibility to theme them from an external perspective...

Use well-written components, or import them locally and tweak them yourself. Same as you have to do for JS libraries.

> Totally invalid argument !

As a language designer, it's my responsibility to give people the power they need, but also prevent them, as much as possible, from shooting themselves in the foot with that power.  JS doesn't let people access raw pointers, so you can't segfault a computer like you can in C.  This is a limitation, but it's worthwhile.

(And note that there *are* languages that prevent infinite loops, like GLSL, but it's an annoying enough restriction that general-purpose programming languages have generally made the tradeoff that the possibility of infinite loops is worth the usefulness of unbounded looping constructs. It's always about tradeoffs, it's not a dogmatic "allow everything!" or "restrict everything!".)

> I have seen this argument many times

Speculating about which argument is "real" is incorrect; I gave you the reasons, and this is *one* of them.

We make decisions not to adopt features that would be to slow to use all the time. When you give people a feature, they're going to want to use it, which just makes sense.

> Could you share please links ?

Unfortunately, most of this conversation took place in person, or in Google Docs, etc. This was before we switched to using GitHub to track everything. However, you can find discussions about this by searching the [old mailing list archive](https://lists.w3.org/Archives/Public/www-style/) for "shadow DOM".

-- 
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2963#issuecomment-410022408 using your GitHub account

Received on Thursday, 2 August 2018 18:23:21 UTC