Chromium developers have announced that they plan to remove support for HTTP/2 server push from the browser engine. Does it affect this article in anyway. Or, every guideline mentioned in this article for moving to http/2 is still valid?
Egalitarian. I enjoy the web, empowering people, creative problem solving. Once took a manager's bug and turned it into 7-14 million USD projected annual return.
h2 server push doesn't change the info in the article. Server push required http headers that resulted in the client receiving more files. There are recommendations and depth relevant to performance at designsystem.digital.gov/performan... in particular domain splitting is now an antipattern and there's a threshold where the number of files can benefit from bundling techniques, possibly starting around 50 files, or more perhaps depending on the server and situation. My takeaway recommendation is to setup using h2 without concatenation/sprites and similar old-school optimizations, use a service worker, make sure to load the minimum of required assets initially. Then tinker with performance as needed measuring performance along the way to see the real impact for the specific situation. These optimizations take time and are a cost so this overall should ease development because it's generally simpler while also providing good performance from the beginning.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Chromium developers have announced that they plan to remove support for HTTP/2 server push from the browser engine. Does it affect this article in anyway. Or, every guideline mentioned in this article for moving to http/2 is still valid?
h2 server push doesn't change the info in the article. Server push required http headers that resulted in the client receiving more files. There are recommendations and depth relevant to performance at designsystem.digital.gov/performan... in particular domain splitting is now an antipattern and there's a threshold where the number of files can benefit from bundling techniques, possibly starting around 50 files, or more perhaps depending on the server and situation. My takeaway recommendation is to setup using h2 without concatenation/sprites and similar old-school optimizations, use a service worker, make sure to load the minimum of required assets initially. Then tinker with performance as needed measuring performance along the way to see the real impact for the specific situation. These optimizations take time and are a cost so this overall should ease development because it's generally simpler while also providing good performance from the beginning.