4 ms·
That would absolutely wreck performance, particularly startup times. You're not going to beat the performance of having 100 open tabs share the same highly opti
by bgirard 6y ago
That would absolutely wreck performance, particularly startup times. You're not going to beat the performance of having 100 open tabs share the same highly optimized PGO-ed browser runtime by replacing that with 100 different runtimes. You're talking about downloading and keeping a small browser engine in memory for every page.
- dmux 6y agoI've not seen PGO before, are you referring to this? https://en.wikipedia.org/wiki/Profile-guided_optimization https://en.wikipedia.org/wiki/Profile-guided_optimization
- bgirard 6y agoYes, Chrome just made recent changes to their PGO: https://blog.chromium.org/2020/08/chrome-just-got-faster-with-profile.html https://blog.chromium.org/2020/08/chrome-just-got-faster-wit...
- deleted 6y ago[deleted]
- slmjkdbtl 6y agoVery true, I'm talking about an unlikely scenario where HTML/CSS/JS is an unpopular need. Yeah there's no solution that'll fit every one's need.
- bgirard 6y agoYou can actually get a decent half-way hybrid by shipping WASM but still binding to HTML and using rich Web APIs as appropriate.