Custom Elements v1: Reusable Web Components
developers.google.com
Custom Elements v1: Reusable Web Components
1–10 of 41 posts
Re: Custom Elements v1: Reusable Web Components
#2Interesting. Only in Chrome 54/Safari 10.1/Opera 46 so far.
http://caniuse.com/#search=web%20components
But there's a polyfill, and more discussion here:
https://developers.google.com/web/fundamentals/architecture/...
Re: Custom Elements v1: Reusable Web Components
#3Custom Elements v1. Designed by committee: https://pbs.twimg.com/media/DALwpYnUAAESRjr.jpg
Polymer. Designed by people who actually do web development: https://pbs.twimg.com/media/DALwpYWVoAAIvkQ.jpg
Re: Custom Elements v1: Reusable Web Components
#4Custom Elements v1. Designed by committee: https://pbs.twimg.com/media/DALwpYnUAAESRjr.jpg Polymer. Designed by people who actually do web development: https://pbs.twimg.com/media/DALwpYWVoAAIvkQ.jpg
Custom Elements is the low-level API that allows you to do all kinds of things.
Polymer is designed to sit on top of that as a higher-level API.
This is how things should be. Otherwise you get designed into an undesirable corner. (Example: I can imagine improvements to the Polymer code achieved with decorators and TypeScript, for example, which would require a somewhat different API. To need a translation layer over that for evermore is undesirable.)
Re: Custom Elements v1: Reusable Web Components
#5[deleted]
Re: Custom Elements v1: Reusable Web Components
#6This article has been added 5 days ago [1], in case anyone is wondering how recent it is.
[1]: https://github.com/google/WebFundamentals/commits/master/src...
Re: Custom Elements v1: Reusable Web Components
#7Custom Elements v1. Designed by committee: https://pbs.twimg.com/media/DALwpYnUAAESRjr.jpg Polymer. Designed by people who actually do web development: https://pbs.twimg.com/media/DALwpYWVoAAIvkQ.jpg
Custom Elements is the low-level API that allows you to do all kinds of things. Polymer is designed to sit on top of that as a higher-level API. This is how things should be. Otherwise you get designed into an undesirable corner. (Example: I can imagine improvements to the Polymer code achieved with decorators and TypeScript, for example, which would require a somewhat different API. To need a translation layer over…
I seem to recall IndexedDB was designed with the same thinking and that hasn't worked out so well.
(Not talking about Custom Elements here since I don't know enough about it - the comment is levelled at the process).
It's all too easy for people in a committee to manufacture the idea of some mythical figures further along the conveyer belt who will magically make something useful out of a giant specification with gaping holes.
Re: Custom Elements v1: Reusable Web Components
#8Custom Elements v1. Designed by committee: https://pbs.twimg.com/media/DALwpYnUAAESRjr.jpg Polymer. Designed by people who actually do web development: https://pbs.twimg.com/media/DALwpYWVoAAIvkQ.jpg
Your comment is unnecessarily snide / cynical; you should be aware that the Polymer team is the main driver of the Custom Elements committee. Polymer 2 is now a framework on top of the Custom Elements standard they helped develop and flesh out with Polymer 1.
Re: Custom Elements v1: Reusable Web Components
#9Custom Elements v1. Designed by committee: https://pbs.twimg.com/media/DALwpYnUAAESRjr.jpg Polymer. Designed by people who actually do web development: https://pbs.twimg.com/media/DALwpYWVoAAIvkQ.jpg
Apart from what others have mentioned about how the Polymer team contributes to the standard, as someone who's worked with Polymer, I think you're also painting a far too rose picture of Polymer, unfortunately.
Re: Custom Elements v1: Reusable Web Components
#10Excellent tutorial, as usual from Eric Bidelman. It's a lot of information to digest though, one should take time with all the different bits and pieces covered in this article.