[spankalee]

Web Bundles is a fundamental solution to the problem bundlers start trying to solve. We need more browsers to get behind that.

After Web Bundlers are natively supported, bundlers can honestly focus on the build-pipeline problem area they naturally evolve into.

[erikpukinskis]

Personally, I take the “run everywhere the same” aspect of web sites very seriously, so I don’t think bleeding edge browser features are an important part of the solution for me.

I also don’t think “build pipelines” are part of the solution.

But I do support you pursuing your vision of finality. Mine is pretty different, you can look up “browser bridge” on NPM if you are interested.

[spankalee]

Every widely supported feature was once a bleeding-edge feature.

I'm not sure how you can about finding fundamental enduring solutions to platform gaps that user-space tools solve without adding platform features. That's always going to create a period where some browsers support a feature and some don't, and we've _always_ had to deal with that. It won't be different here.

I mention build pipelines because that's what most bundlers actually are. If they drop the bundling part, they can just focus on that.

[erikpukinskis]

I think platforms “mature”, and nothing important happens after that. The web was mature around the time WebGL was widely adopted. Bundles don’t do anything we can’t already do. They just make the web more brittle.

Which means: lovely for you, until something snaps.

For me that’s two cons: lost users, and a more complex data model. And no pros.

[pjmlp]

The way things are going it suffices that Chrome and Safari do it.

[spankalee]

I really hope that by separating Web Bundles from signed exchanges that Firefox will get on board. And I really hope that Firefox retains and gains relevance somehow.