Slashdot Mirror
The State of the Internet Operating System
macslocum writes "Tim O'Reilly: 'I've been talking for years about "the internet operating system," but I realized I've never written an extended post to define what I think it is, where it is going, and the choices we face. This is that missing post. Here you will see the underlying beliefs about the future that are guiding my publishing program as well as the rationale behind conferences I organize.'"
This whole "Internet OS" thing reminds me of the periodic resurgences of the dumb terminal/thin client idea that goes back to the mainframe days. It seems like every ten years or so, everyone is talking about thin clients in every office, with the OS and apps running on some offsite server somewhere (now with the added twist of multiple servers over the internet). Ostensibly this is seen as a good way to save IT money and overhead. But in every actual deployment I've seen, it only causes hassles, additional expense, and headaches.
Back in the 90's we tried this at my old university. We networked all our computers and put all our apps on a central server. Even though this was all done on a local network (much more reliable in those days than the internet), it was still a complete disaster. Every time there was a glitch in the network; every student, professor, and staff member at the university lost the ability to do anything on their computer--they couldn't so much as type a Word document. Now, with little network downtime, you would think this wouldn't be so much of a problem--but when you're talking about thousands of people who live and die by the written word, and who are often working on class deadlines, you can imagine that even 30 minutes of downtime was a nightmare. I was skeptical of this system from the get-go, but got overruled by some "visionaries" who had bought into the whole thin client argument with a religious fervor. Of course, long story short, we ended up scrapping the system after a year and going back to the old system (with a significant cost to the state and university for our folly).
SJW: Someone who has run out of real oppression, and has to fake it.
If were a living thing, it would have cancer, several kinds of it, spread all around the body. Botnets, zombies armies, spam, malware sites... a good percent of it is just badly sick. It have several brains too, some of them playing against the health of the whole body by not letting the "blood" flow freely all around, as some governments censoring it because political reasons or lobbying ones.
It have its strengths too, is maturing (hopely), have a good defense system so the sickness spread around don't infect everything, and it evolves fast (even if limited by laws, patents, trolls, etc), getting more personal and localized.
With a bit of luck people, institutions and governments starts to worry about its health, the ecosystem that it is and start working on preserving it as much as the planet we live.
I think that's where old-school software download sites shine again. They are basically app stores for free/shareware apps; and they've been around for decades.
With the advent of Google-level search engines, they became a lot less relevant. Now that Google & co are spammed to death, they regain part of their old glory.
It's not all black and white though. App-stores suffer from fraudulent entries that try to game the system, too. I've followed the reports of various Apple App Store developers for a while and even though Apple is tough, a lot of dubious crap falls through the cracks. On the other hand, Google tries to combat sites that try to game their ranking algorithm (and fails miserably).
O'rielly is pointing out the same dangers of the Cloud as Stallman, but in a reasonable voice. The question is how to preserve the DIY environment when hardware is sealed (see iPad) and software is ran on corporate computers. Will innovation be constrained or will the cloud be open enough to allow people to change vendors easily without total reworks?
Not really. Your situation of working offline is a particular case of working online. It just happens to have high latency. So the easiest solution, for the user, is one which generalizes to encompass high latency.
The converse is not true. Of course you can retain the capabilities of an offline environment even after you add a wire to it, but those capabilities do not generalize to managing the resources on the other end of the wire.
The easiest solution to implement is a pencil and a piece of paper. Oh, you want capabilities too? Well, that's different.
Parity: What to do when the weekend comes.
And the easiest solution, which seems to escape almost everybody, is "don't work offline in the first place".
FTFY. Having my data available on any online computer or device that I happen to be at *increases* its availability to me, even in the presence of occasional outages. There's down-sides, such as privacy, but availability isn't one of them: it's a net positive.