Re:Microsoft Fast Design
by dmitriid on Friday August 07, 2020 @04:27PM
(#24086098)
> Is the only thing that stops components from colliding literally naming convention? Like <fast-dropdown> != <my-homebrew-dropdown>? So it's basically a convention-based standard rather than a fixed standard?
Yup :) They decided to go for a flat namespace where all that distinguishes between components is their name. I'm guessing this already leads to collisions between different versions of the same element. And there has been an open issue for it for three years now: https://github.com/w3c/webcomponents/issues/716 And the "solution" seems to be "let's add more Javascript": https://github.com/justinfagnani/scoped-custom-elements
> I do feel I am exposing myself to some ridicule for being out of style and I regret my attitude in my original reply
It's perfectly fine :) I've been way more rude about web components before (and still am :) )
> My main fear that I developed over the years is we end up developing frameworks for frameworks instead of delivering tangible results.
Indeed. That's my main gripe with web components, really: instead of providing tangible benefits to developers, they ended up being "an API primarily for library and framework developers"
Yup :) They decided to go for a flat namespace where all that distinguishes between components is their name. I'm guessing this already leads to collisions between different versions of the same element. And there has been an open issue for it for three years now: https://github.com/w3c/webcomponents/issues/716 And the "solution" seems to be "let's add more Javascript": https://github.com/justinfagnani/scoped-custom-elements
> I do feel I am exposing myself to some ridicule for being out of style and I regret my attitude in my original reply
It's perfectly fine :) I've been way more rude about web components before (and still am :) )
> My main fear that I developed over the years is we end up developing frameworks for frameworks instead of delivering tangible results.
Indeed. That's my main gripe with web components, really: instead of providing tangible benefits to developers, they ended up being "an API primarily for library and framework developers"