>> You could have used a service worker and cache things in order to get the same thing, combined with progressive web applications for installability.
This is true, but I think ergonomics of an encapsulated page/application make it easier to reason about for very large applications. Maintaining the service worker and the cache at scale can become a barrier to entry for some developers and applications. On Tuesday, May 24, 2022 at 10:12:33 AM UTC-7 PhistucK wrote: > Not that I am against, but does this unlock previously locked > opportunities in the specific examples you just mentioned? > You could have used a service worker and cache things in order to get the > same thing, combined with progressive web applications for installability. > > ☆*PhistucK* > > > On Tue, May 24, 2022 at 4:35 PM 'Ben Mathwig' via blink-dev < > [email protected]> wrote: > >> Microsoft has a strong interest in seeing this feature ship. We believe >> that sub-resource bundling is opening the door to a new way of shipping and >> delivering offline web applications, changing the traditional definition of >> “web application”. >> >> Here are some ways Microsoft products can take advantage of this: >> >> *PowerApps* >> >> Microsoft PowerApps allows a developer to author an application and >> deploy to iOS, Android, and the web. The first two platforms allow >> applications to be deployed and used when the device is offline, but the >> latter is currently not “installable” on the device. Web bundling could >> unlock the capability for a web application to be “installed” on a device >> to operate offline. >> >> *Office Online* >> >> Office productivity web applications are a perfect example of >> applications that could benefit from a packaged bundle of application >> resources. Combined with local storage APIs, this could help developers >> reach communities that have little to no network connectivity. >> >> >> >> While there have been concerns brought up by the community, we welcome >> the opportunity to collaborate on addressing these issues in the next >> iteration of this project. We feel confident we can resolve them in a way >> that preserves the integrity of the open web. >> >> >> Ben Mathwig >> Senior Product Manager >> Microsoft Edge Web Platform >> >> >> On Sunday, May 22, 2022 at 6:28:50 PM UTC-7 [email protected] wrote: >> >>> Hello >>> >>> I am sharing the feedback from the Origin Trial with 12 participants: >>> >>> - >>> >>> 10 of them responded "Extremely likely" to "How likely are you to >>> keep using this feature?" >>> - >>> >>> Qualitative feedback: >>> >>> >>> - >>> >>> "I'm very excited about the CSP interpretation change rolling out in >>> M92" >>> - >>> >>> "looking forward to the CSP fix!" >>> - >>> >>> "I'm very glad you're working on this!" >>> - >>> >>> "This feature is great! I'd love to see it fully launch" >>> >>> Daisuke >>> >>> >>> On Sat, May 21, 2022 at 5:38 AM 'Jeff Kaufman' via blink-dev < >>> [email protected]> wrote: >>> >>>> Thanks, Otto! As someone who used to work on mod_pagespeed I wanted to >>>> give a bit more context on how web bundles improve on what is possible for >>>> automatic site optimization tools like mod_pagesped: >>>> >>>> 1. Combining many small images into a single file otherwise requires >>>> spriting (with css to identify which area of the image you want for each >>>> usage) and mod_pagespeed's ability to do that automatically (sprite_images >>>> filter <https://www.modpagespeed.com/doc/filter-image-sprite>) is >>>> limited. It needs to understand the site's css and the publisher needs to >>>> have already set their css up to minimize the changes required. With >>>> bundles it is much simpler: you put all the tiny image files in the >>>> bundle, >>>> and you rewrite the URLs to point into the bundle. >>>> >>>> 2. Combining many small css or js files into a single file (combine_css >>>> <https://www.modpagespeed.com/doc/filter-css-combine>, combine_js >>>> <https://www.modpagespeed.com/doc/filter-js-combine>) requires hacks >>>> to prevent invalid css or js from breaking the rest. It's reasonably >>>> common that publishers will have <link rel=stylesheet href=invalid.css> >>>> that doesn't parse, and if you blindly concatenate with other css you will >>>> change the layout on the page. Since automatic site optimization tools >>>> like >>>> mod_pagespeed want to make the site load faster without making any changes >>>> to how the site looks, that isn't acceptable. Same issue with js. >>>> >>>> 3. Today you need to have separate files for combined images, css, and >>>> js. With web bundles there can be just one. >>>> >>>> Jeff >>>> >>>> On Friday, May 20, 2022 at 1:11:16 PM UTC-4 Otto van der Schaaf wrote: >>>> >>>>> As a maintainer of mod_pagespeed <https://www.modpagespeed.com/>, I >>>>> would love to see this ship. >>>>> >>>>> >>>>> On Wednesday, May 4, 2022 at 5:42:15 PM UTC+2 slightlyoff via >>>>> Chromestatus wrote: >>>>> >>>>>> Microsoft would like to see this ship ASAP. LGTM1 >>>>>> >>>>> -- >>>> >>> You received this message because you are subscribed to the Google >>>> Groups "blink-dev" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> >>> To view this discussion on the web visit >>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/45f97f97-7db0-42ee-bea8-d01ddb344ba6n%40chromium.org >>>> >>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/45f97f97-7db0-42ee-bea8-d01ddb344ba6n%40chromium.org?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "blink-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> > To view this discussion on the web visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/81ea3aac-58c3-4a77-941a-b647c03b2edfn%40chromium.org >> >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/81ea3aac-58c3-4a77-941a-b647c03b2edfn%40chromium.org?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/999d3ef7-1ccc-4dd4-9b57-300a8f24200cn%40chromium.org.
