On Wed, Jul 15, 2015 at 12:00 AM, <mar...@marcosc.com> wrote: > * It's not clear what problems manifest solves
This is by far the biggest problem. I think we ended up with manifests because packages have manifests and iOS/Android use packages for applications, but none of that translates well to the web. > * Extra HTTP request could yield a performance penalty (even if > deprioritized)... though probably not a concern in a HTTP2 world. It's still a concern. You'll still need to duplicate all the metadata that the client needs immediately in the HTML. One reason that was mentioned in favor of manifests was "don't repeat yourself". The way the web has dealt with that for two decades is server-side templating. If this was really the core concern we should figure out client-side templating for HTML, since this does not just affect document metadata. I agree with Martin that focusing on concrete problems to solve is a more worthwhile endeavor. -- https://annevankesteren.nl/ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
