3 ms·
Layouts that don't change can be heavily cached. ... and having the chrome performance depend on that infrastructure is significant incentive to do that cachin
by shadowgovt 4y ago
Layouts that don't change can be heavily cached.
... and having the chrome performance depend on that infrastructure is significant incentive to do that caching and other pipeline cleanups.
(At the very least, having one fewer UI toolkits to maintain will let Mozilla engineers focus their efforts).
- gmueckl 4y agoCaching is only amortizing if the exact same computation is repeated exactly. And even then, the first full computation is slowed down by a failed cache lookup at the beginning and all code paths that can lead to cache invalidation now have to test for that and trigger it.
- shadowgovt 4y agoNone of these facts imply that either CSS lookup cannot be sped up by caching or XUL didn't already have those concerns. And for something like the browser chrome, the cache could even be serialized during compilation and loaded in to prime it when Firefox launches. It's possible to build a slow CSS engine and it's possible to build a fast CSS engine.