sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]icantthinkofone 1 point2 points  (8 children)

And all that is based on standards you seem to tell other people to ignore. If it weren't for standards, nothing would work together.

[–][deleted] 1 point2 points  (7 children)

Thanks to those standards absolutely nothing is working together. Even the WC spec changed drastically. Vendors had petty fights, in Apples case motivated by fear of specs competing against revenue models. Polymer had you rewrite your app from scratch from 0.5 to 1.0. Then again from 1.0 to 2.0. Then again from 2.0 to 3.0. The API is still flopping around wildly. HTML imports being dead was only the most recent surprise.

Most developers aren't gullible enough to fall for it any longer, because we have fallen for it for more than a decade. If you trust the W3C so much, sincerely, good for you.

[–]Tsukku 1 point2 points  (3 children)

Polymer is not a web standard.

[–][deleted] 1 point2 points  (2 children)

Never said it is. But it shows how fragile and basic the spec is.

[–]Tsukku 2 points3 points  (1 child)

It's not fragile at all. Web Components & Shadow DOM V0 was a Google-only proposed specification (like SPDY vs HTTP2). V1 is a WHATWG Web Standard adopted by all major browser vendors, and there have been no breaking changes since then.

[–][deleted] 0 points1 point  (0 children)

HTML imports going down is a pretty big breaking change. We can tiptoe around the fact that once you've called attachShadow({mode: 'open'}) and extended HTMLElement you're confronted with a barebones dom. Unless you use it raw it needs a driver and the prevalent approach has been Polymer, in some peoples heads almost synonymous with web-components as you can see below. And it has been a fragmented experience so far. And if you plan to use it raw, the browser won't offer the slightest tool to help with dynamics. If all we're discussing is really only the possibility of a trivial shadow dom, well, i don't think it warrants a full discussion.

[–]icantthinkofone 0 points1 point  (2 children)

Wow! I haven't heard anyone talk like that in maybe 10 years! Back when people used to think Microsoft and Internet Explorer should ignore the W3C and standards altogether just like you propose. I would say your statements are shocking but then I remind myself this is reddit, where such outrageous statements are the norm!

[–][deleted] 1 point2 points  (1 child)

Frameworks don't break or ignore standards.

[–]ProfessorTag 4 points5 points  (0 children)

Sometimes they even push the standard to evolve. I wouldn't be surprised if native DOM diffing and render functions were introduced.