Okay, an iBook is out, so…what would it actually take?
And I don't mean to reinvent the LC.
For the sake of argument, say we've got the bones of a generic laptop. And all it's bits.
Also for the sake of argument, let's assume this thing has some sort of a backup battery to keep the PRAM, CMOS or whatever from dying, and has decent connectivity options.
And if you think that's far-fetched…
I've got ideas for an OS to run on this beast, but like the deck, it exists only in my head right now. Completely awesome concepts, it would point and laugh at Second Life, make telecommuting a joy, and change the internet forever.
Here's how it'll work, if I can rope in some programmers… (wishful thinking)
Stage 1
What I propose here is a stand alone App. Just so a person can move around in a room and maybe do stuff. Coded to run as low-end as possible, that way it won’t keep people like me out of the loop. Proof of concept.
Once there is a room or rooms, with objects you can interact with, we (you) can improve the envionment with, say, a computer terminal that you can use to word process or a stereo that will access mp3s or audio tracks on a CD. Basic stuff.
Stage 2
Client and server. Have a machine dedicated to serving an environment, and log into that environment with a client.
This would be where some sort of basic connectivity would come in handy, Ethernet, FireWire, Wireless, whatever would be easy.
This would also be where the coding for low-end machines would come in handy. Because the server need only hold an array of data, as a space, the client could handle all the heavy GUI work.
further to this, move to distributed processing, where each server would contribute to the total load. (In theory)
If a machine can handle it, also use multiple network protocols, most machines have Ethernet, USB2, FireWire, and perhaps wireless. A possible scenario would be to use a LAN for heavy traffic, and wireless for the light stuff. Whatever works. (In theory)
I suggest this with a view to avoiding connection to the internet unless needed to retrieve data or send email. We do not want to distribute processing in real time over the net. It would clog it up for everyone else and cost you and others money. Wireless P2P would avoid all this.
Stage 3
Move from Client/Server, to OS level so the environment can talk directly to the hardware, without incurring overhead load from an separate OS. Full on service development can start here. Imagine using the GUI environment as you might a commute to work, a walk in the park, or a good old-fashioned punch on against an opponent Oni-style, all in good fun and arse kickery of course. Done in a different domain, so you can’t punch out your co-worker or boss in the office.
Stage 4.
Imagine the internet as seen through a 3rd person perspective GUI instead of just a web browser. Very Gibsonesque, but damn it’d be fun!
That's it.
Seriously though, IF this was a reality, at least we'd have a better choice of OS to run on our boxes or decks or whatever, OSX, Windows, *nix, or UnityOS (what I'd call it.)
Laugh if you want, but i reckon it's doable. I've been booting the idea around for over two years, and I think I've gotten several of the kinks worked out.
At the very least, it makes good fiction. :'(
Nick
(runs and hides)
