4 ms·
Whoever gets to "1Ghz per user" in the cloud first, wins. Reason: with the future being a socket per user over which the HTML5 interface is streamed, the user
by pcunite 11y ago
Whoever gets to "1Ghz per user" in the cloud first, wins.
Reason: with the future being a socket per user over which the HTML5 interface is streamed, the user experience can be speedy if that same socket has a dedicated core too. I really want 2Ghz per user, but let's not be greedy.
- dogma1138 11y ago1Ghz is a meaningless number I assume you base it on current IPC performance of desktop CPU's which is completely irrelevant.
- pcunite 11y agoJust trying to represent time.
- dogma1138 11y agoStill not sure what are you getting at. If your proposed system is basically a time-sharing system which thin-clients connect too then it's performance needs to be similar to what currently individual desktops would need. If all of the processing isn't done on your system (e.g. 3rd party could like Office 365, or in your own desktop e.g. Desktop Office) then why would you need it in the first place?
- username223 11y ago> the future being a socket per user over which the HTML5 interface is streamed, That is a future in which I want to open my virtual veins in a warm bathtub. If the future is mediocre and likely surveillance- and ad-supported software shoved through a standard originally designed for formatted text, we have a problem.