> The requests comparison is being made between polyfilled HTML imports without HTTP/2 vs. a single pre-bundled request.
Bundling is a necessity b/c of the limitations of http1.1. For h2, large bundles are an anti-pattern. The comparison is apples to oranges.
HTML Imports are one way to solve the dep problem, but you also don’t have to use them. You’re free to use whatever import/loader/bundling/build tools you want. For example, the Polymer team built Vulcanize to crush the Import tree into a single file (stop-gap for http1.1 users). But the tool also allows you to exclude resources via URL. If you want to load your own version of jquery or bundle it in differently, totes can!
> “not bringing enough attention to the potential downsides of adopting WC” …
I think with any new technology, you have to measure the tradeoffs and costs of adopting that technology in your own setup. It’s case by case. I’ve built a lot of production apps using web components (so have a lot of other people). Talking about tradeoffs are good, but I also sees tons of misconceptions on this stuff. It’s important to clarify and show data.