> Re point 1: the problem being that the moment you introduce a specific data flow solution
Eric Bidelman

HTML imports depends on:

  1. All target audience browsers implement the spec
  2. All target audience browsers properly support HTTP/2

Otherwise it would end up with worse initial load performance due to the orders of magnitude more requests. Now, the marketing around WC/PWA/HTML imports is heavily focused on “slow phones on 3G networks” — and what is the chance of a user in this scenario having an up-to-date browser that supports all these new features? I’m not very optimistic about that. So there’s a fair chance that adopting the full WC/HTML import stack today ends up bringing worse UX to the very users you are trying to help, no?

Show your support

Clapping shows how much you appreciated Evan You’s story.