Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587)

What I really miss in the whole journey of Web Components - which lasts for more than 7 years now - is a holistic approach to software engineering. What means [holistic](https://www.merriam-webster.com/dictionary/holistic)?
>  relating to or concerned with wholes or with complete systems rather than with the analysis of, treatment of, or dissection into parts

This practice of forcing ES6 `class` syntax really breaks this reasoned principle of holistic software. Guys if you design software API's this means you have to think about all possible consequences, various browsers, various JS engines, polyfills, transpilation, etc. etc. Why aren't you applying a holistic approach? I mean Web-Components aren't just a new JS library, they are a whole set of new browser APIs and have to work reliable.
It belongs to professional software engineering, it's part of your job, I really don't understand this standard of work.

Another product of yours I really disagree is releasing the `<template>` spec as living standard without any standard template feature like interpolation, conditionals, loops, partial you name it.
I mean you can find the definition of *template* in any dictionary, and there are lots of good examples out there in various programming flavours of what a template is. And which product do you release? You just provide a plain `<template>` tag and call it finalised living standard. I admit it would be an awesome geek joke at late night comedy. Unfortunately we (web developers) have to work with it.

On the other side I thank you, this way I get costumers asking me to poke with their problems, problems which could be avoid though...

If you don't change your approach, get properly organised and make sure to understand the technical words, your project of web components will fail broad adoption and leads to blog posts like:
https://dmitriid.com/blog/2017/03/the-broken-promise-of-web-components/

-- 
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/587#issuecomment-374873359