Hacker News Reader

Everyone wants to implement it (and is implementing it!), with the exception of HTML imports, which are likely going to get dropped from Chrome eventually.

View on HN

Are HTML imports not saved by widespread http2 adoption, where the imported pages are pushed to the client upon initial page request? No reason to throw it out completely.

They are killed by ES6 import spec.

So, "declarative custom components" have fully devolved into "JS-only framework that pretends to be DOM and adds weird limitations"

It's not quite so clear cut, AFAIK, rather wanting to wait and see how ES6 imports end up getting used rather than speccing and implementing something similar for HTML imports.

Reply on news.ycombinator.com