3 ms·
From the keyboard of a Chromebook Pixel I think I can feel where this is going. I can see a time when ChromeOS works on this internal Google network for most of
by Theodores 9y ago
From the keyboard of a Chromebook Pixel I think I can feel where this is going. I can see a time when ChromeOS works on this internal Google network for most of what it does, running on protocols that are orders of magnitude quicker than regular 'https://' https://' style TCP/IP networking.
There is this danger that these pieces Google work on get joined up, e.g. Android apps on your Chromebook. With Google owning the network from the server 'encapsulated' over public networks and then on Google's own home router and on to Google gadgets like Chromebooks, there is a high likely hood that some glorified 'SPDY' that hooks in at OS level is going to happen. Therefore pieces of the puzzle may not have any obvious benefit, to take a train analogy, who would build a railway through Utah? On its own it might not make sense but as part of a transcontinental railroad it was an important part of the puzzle to get done. With Google there is some of this shrewd aspect with added 'moonshot' thrown in for good measure.
- wmf 9y agoIt's already happening with QUIC. Google is backporting as many improvements as they can into the traditional network stack though, like HTTP/2, BBR, and TLS improvements.