I have worked on teams where we rushed to deploy things that we knew should be faster or more resource efficient. The incentives are simply not aligned right now — it usually pays to get stuff out even if it’s a bit slow, and the cost of browser resources are not yours to bear. This results in webpages with janky rendering (the Mighty home page itself may be guilty of this) or web apps with performance issues.
Implementing the browser as a VNC client is a clever approach but seems to be a band-aid for browser performance instead of attacking root cause. Shifting the incentives for product development teams could be a more permanent solution. Perhaps by imposing stricter resource restrictions in the browser or by adding performance metrics to search engine algorithms that go beyond initial load time.
EDIT: Reading other comments, it sounds like the founders have ideas for the cloud browser that go beyond performance. I’ll be curious to see how this plays out.
Implementing the browser as a VNC client is a clever approach but seems to be a band-aid for browser performance instead of attacking root cause. Shifting the incentives for product development teams could be a more permanent solution. Perhaps by imposing stricter resource restrictions in the browser or by adding performance metrics to search engine algorithms that go beyond initial load time.
EDIT: Reading other comments, it sounds like the founders have ideas for the cloud browser that go beyond performance. I’ll be curious to see how this plays out.