Windows Is Dead – Long Live Midori?
parvenu74 writes "A story from Infoworld is suggesting that the days of Windows are numbered and that Microsoft is preparing a web-based operating system code-named Midori as a successor. Midori is reported to be an offshoot of Microsoft Research's Singularity OS, an all-managed code microkernel OS which leverages a technology called software isolated processes (SIPs) to overcome the traditional inter-thread communications issues of microkernel OSes."
web-based == subscription model.
12:50 - press return.
It doesn't...they are describing a thin client. While I agree that thin clients are nice in a lot of situations, there is no way in hell I would use a thin client as my primary OS. And I will not use a thin client at all (well, outside of a corporate/work environment anyway) unless *I* control the server for it. If I want to put a couple thin client terminals around my house that run off my Linux server, fine. I'm curious how they think a thin client will work as a primary OS anyway. It won't...you have to have SOME OS on the computer. And I really don't think anyone is going to be using PXE over the internet.
I hope you're being sarcastic, because Midori is just a feminine Japanese name meaning green.
rehab is for quitters
No, she's an anime character!
"16MB (fuck off, MiB fascists)" - The Mighty Buzzard
The Eee and its ilk have shown that people are willing to buy Windowsless boxes, which is an affront to Microsoft's business model. You have to wonder if Midori is a "plan B" to allow them to continue to get revenue from Linux users. Alan, Bob and Clarence may well be willing to pay $10 a month for "Windows access" on their Eees if it lets them use Office, and this way Microsoft have a guaranteed revenue stream whatever OS people actually buy with their machine. Especially if it's agressively marketed and bundled.
No kidding!!! What do you say at this point?
This probably means that M$ is going to add a bunch of proprietaries to Javascript through IE and start adding language features to make a proprietary platform. Even so more, probably access to the win32 api via javascript. Even more so, probably JITed c#, wait.. wasn't java supposed to do this?
This is almost exactly the same thing, in spirit at least, as Inferno (http://www.vitanuova.com/inferno/), which started in 1995 and has been under continuous development since. Managed kernel, runs on real hardware, uses software isolation between managed threads... oh, and has code flying, for real, right now. :)
Anarchy$ dd if=/dev/random of=~/.signature bs=120 count=1
It seems that every ten years, someone re-invents the thin client.
First it was dumb terminals connected to a mainframe, then to a serial port box so one can connect to a UNIX box.
Then came XStations which used various (direct, indirect, broadcast) forms of XDMCP to find a host to download microcode and run apps from.
Then, it was JavaStations where people talked about fast broadband access to stuff on the ISP's server, and not to worry about all their private documents being stored offsite.
This just seems like more of the same, perhaps an offshoot of cloud computing. It will work for a couple niches here and there, but as a whole, Net based operating systems will fail, as people want to keep their stuff private on their own systems.
Same disadvantages apply. Security of stored files for example -- I trust my external TrueCrypt encrypted drive that uses both a long passphrase and a set of keyfiles a lot more to securely store my Word documents than I do some random ISP's computer.
"Midori" is Japanese for "green". It is also a common female first name.
I don't know how either would apply to an OS, unless it has some connection to this.
Prov 9:8 Do not rebuke mockers or they will hate you; rebuke the wise and they will love you.
Brian Madden is either talking about something else, or he's confused by references to hypervisors elsewhere. Midori will run under Hypervisors... but as one possible deployment of the OS, not as an essential part of the system. Singularity is more like ".NET" taken to the next level, with the entire OS running without hardware memory protection (let alone hypervisors), so it can run anywhere... even as a module inside another application... without any specific hardware support.
...but that it is based on a new programming model. Many ideas are coming from the programming languages research community. All code will be type-safe and memory-safe. Interaction with the OS and other processes will make much more use of immutable data structures. Concurrency will be pervasive. It will be like one giant Erlang environment.
I mention America specifically as a generic example that everyone understands for one reason. "Unlimited Internet Bandwidth". This type of a model (even if it is a model where MOST of the OS is on current hardware but then randomly checks the internet for it's main "modular" pieces, vs having it all on the Hard Drive as we current do) cannot work well because other countries actually have to pay for speicifc amounts of bandwidth.
And even now, I've read random articles talking about ISPs (in america) which are considering moving to the "Pay for Bandwidth Tiers" models. WTF is the point of getting an OS that eats up all of your bandwidth just to stay turned on and be running a screen saver? It would need to randomly connect out and update things after all...
Some might argue that this is already being done, and that "caching" would solve the problem ... except that caching would negate the whole purpose of an online-OS (it needs to always have the latest thing to work well). Currently windows ALREADY connects out and randomly checks things and uses bandwidth, but it's NOT downloading entire modules as something like that would require.
Sorry, but if I lived somewhere with Pay-As-You-Go internet (I'm considering moving to Australia) I sure as hell wouldn't pay more money to an ISP on a monthly basis just so that I can use the "latest and greatest" windows.
Anyone remember Cairo? ;-)
Never ascribe to malice that which is adequately explained by incompetence.
Midori is being designed in such a way that components of the OS communicate with each other in a location independent manner. API calls to a local machine are no different than API calls to a remote machine.
This strikes me as being similar to a design goal shared by Plan 9, and its spiritual descendant Inferno, both of which were based around the 9P protocol.
The "cue the foo posts in 3, 2, 1..." posts will commence with no subsequent foo posts in 3, 2, 1...