4 ms·
Exact same thing explains Google's failure with cloud books (Chrome OS)... Inside of the mothership (and to a lesser extent the shuttles) you have a seamless ul
by redwood 15y ago
Exact same thing explains Google's failure with cloud books (Chrome OS)... Inside of the mothership (and to a lesser extent the shuttles) you have a seamless ultra-fast internet connection. This makes a cloud OS without significant client-side caching a promising concept.
However in the real world, when your internet craps out for a few seconds, you go through a tunnel, whatever... or if you live in a developing country with spottier internet access, and you're trying to write a great idea down but can't input text because the connection's dead... well you quit the product.
Hubris.
- j_baker 15y agoDescribing the internet connection on a shuttle as "seamless ultra-fast" (even if to a lesser extent) is laughable. The shuttles use much the same connection as your cell phone uses, which means the connections do crap out for a few seconds or when you go through a tunnel. Plus, if there are too many people using bandwidth-heavy apps, the connection seriously degrades.
- redwood 15y agoBut consider the near-seamless switch from shuttle to mothership wifi. And do remember most people don't have internet on their commuting option at all. This fuels the point that it's difficult to build a successful cloud book if you're essentially optimizing it for your own employees when they're very different from most.