Can You Afford It? Real-World Web Performance Budgets

Re:Can You Afford It? Real-World Web Performance Budgets by mrighele on Saturday October 28, 2017 @08:03AM (#15574865)

I would love to have a way to tell the browser "don't throw away the current DOM, Just apply the differences". It would work nicely in non-js page to make the experience smooth (and would probably work terribly if there was a lot of J's, of course)

[ Parent | on HN ]

Re:Can You Afford It? Real-World Web Performance Budgets by nojvek on Saturday October 28, 2017 @01:06PM (#15575811)

This. Every major client lib out there uses some variant of vdom. If this dom diffing was natively supported, browser would request with current dom hash and server could efficiently reply with a diff that both server and client can compute to be the same new hash.

If it's forms. Client calls server with base hash + changes made by client and server replies with. Base hash + new diff to apply. The new diff includes validation changes.

It's trees and diffs all the way down.

[ Parent | on HN ]

Re:Can You Afford It? Real-World Web Performance Budgets by pcmaffey on Saturday October 28, 2017 @01:10PM (#15575827)

This is exactly what React's virtual DOM does. Maybe the future is making the virtual DOM native to the browser?

Bundle React with Chrome? Or how about a browser package manager that could cache and reuse all these common js libraries used on so many sites?

[ Parent | on HN ]

Re:Can You Afford It? Real-World Web Performance Budgets by discreditable on Saturday October 28, 2017 @09:17PM (#15577567)

DecentralEyes does just that.

[ Parent | on HN ]

Re:Can You Afford It? Real-World Web Performance Budgets by grogs on Sunday October 29, 2017 @07:38PM (#15582192)

Sounds like PJAX.

[ Parent | on HN ]