> The Mighty model is timesharing CPUs. Yeah, but I think it's better to think about it like virtual/remote desktops, where the granularity is a browser tab.

> The Mighty model is timesharing CPUs. Yeah, but I think it's better to think about it like virtual/remote desktops, where the granularity is a browser tab. At least, that's the only way it makes sense to me. I might understand that to do 4k high res 3d on my phone - my phone will need help. And once that "help" is available - my TV, and my tablet and my smart watch can make use of it. But I'm not generally willing to trade latency for cpu time sharing. What is interesting is an always on, always working desktop session. It's why I like screen/tmux and ssh, rdp - and would consider running a Linux terminal server, so my laptop(s) and desktop(s) could be a disk less, stateless thin client. Make the observation that the browser tab is the new process/application granuality - and it makes sense to host tabs in the cloud. Personally I'd want to self host it - but the idea doesn't sound quite so inane.