Re: [w3c/webcomponents] Make JavaScript Files a Valid Entry Point to a Web Page (#807)

> You keep saying what the browser should do but failing to explain why. Beyond prototyping, I don't see any benefit at all. Even then, for anything other than a few elements it becomes unwieldy without some kind of tooling and at that point the tooling may as well just create the boilerplate for you.

Personally, I don't like creating static html files anymore. I think it stupid that a website driven almost elusively by javascript, has to generate html files on the server-side just so the browser will be smart enough to know what to do with the javascript files. Seriously, let's skip this middleman: HTML files. Why should servers have to fool the browser into thinking it is receiving some static html file. Server-side we are dynamically generating these files. Why can't the client-side support this? **Answer:** because just doesn't.



-- 
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/807#issuecomment-486298179