Windows 8 Codename Midori and Windows 9!

[Scorbing]

LOL...This guy is so full of it. Windows 7 is still in diapers and this guy is already talking about Windows 8 and 9!....LOL

Don't you think Microsoft already has enough problems as it is with Vista?

Windows 8 won't be around for another 6 or 7 years so chill out.

[Brandon Live Veteran]

Yeah it's littearly impossible, because at some point you need a machine code level interperter... which almost always has a machine level kernel... even MS's internal demo managed kernel has a native code kernel under it

Well, to be fair, C# and F# are not interpreted languages. They are compiled languages just like C++. They compile at build time to MSIL, which is then just-in-time compiled to native code at run time.

Using just-in-time compilation for an OS may not be ideal, though, so as I recall the Singularity project compiled their C# code into native binaries.

So no, there's nothing impossible about writing an OS in C#. Now, why you would go and do that is another question entirely.

[4CxbqFxVnstmA Veteran]

Midori?

Hmm, a non-English rumor site is purporting that we have some new non-English codename... how large of a salt grain can I buy these days?

Don't Microsoft codenames have to be taken from towns near Redmond?

[jjrambo]

From Windows 7 and so on there will be a new version of Windows every 2-3 years just as MacOS gets updated frequently.

[XerXis]

yeah right, bs

nothing else to say

[jamend]

BS. It is not possible to build an O/S kernel using interpreted code in a language such as C# or F#. Complete and utter fake.

Microsoft Singularity

JNode

These are two operating systems that use a small amount of assembly to boot and wire up their kernels, but the kernels are written in C# and Java.

[+Nik Louch Subscriber²]

The forum rules should be ammended to stop this sort of crap. Posting BS as fact adds nothing to neowin.

As for "Do they have to be near Redmond". Well, Fiji isn't. Isn't the theme "mountains"?

[Angel Blue01]

BS. It is not possible to build an O/S kernel using interpreted code in a language such as C# or F#. Complete and utter fake.

Singularity

[MtnDewCodeRedFreak]

This should be a great joke for Comedy Central's shows, like Jeff Foxworthy, Lisa Lampanelli, and Larry the Cable Guy.

[y_notm]

The forum rules should be ammended to stop this sort of crap. Posting BS as fact adds nothing to neowin.

As for "Do they have to be near Redmond". Well, Fiji isn't. Isn't the theme "mountains"?

codenames are out. we're back to straight version numbers when referring to yet-to-be-branded versions of Windows.

[PL_ Veteran]

Don't Microsoft codenames have to be taken from towns near Redmond?

No. Whistler and Blackcomb are both mountains in the British Columbia. Longhorn is the bar in between the two. To get from Whistler (XP) to Blackcomb (7) you have to go through Longhorn (Vista) first! ;)

Then you've also got Chicago, Memphis, Janus, Cairo, Nashville, Neptune and Oddyssey. And that's just Windows :p

[SakuraKira]

Even if this were true, what is the point of posting about something whose release would be several years away? Even the infamous "leak builds" would be years away. Someone should start a thread about "bizarre Windows rumors I've heard over the years." lol

Whistler and Blackcomb are both mountains in the British Columbia. Longhorn is the bar in between the two. To get from Whistler (XP) to Blackcomb (7) you have to go through Longhorn (Vista) first!

:p

[Ci7]

will windows 8 and 9 both sucks cuz

fanatic , xp fanboys , ABMers , Linux geeks , apple fanboys after few years they will says ;

windows 9 = windows 8 R2

windows 8 = windows 7 R2

windows vista = windows ME R2

"so they will come up with result that windows 9 is windows super duper me bsod edtion and that they are dumbs lol"

window 8 is memory hog

windows 9 copyed MacOSXII

windows 9 send have Super DRM and send bla bla bla to M$

windows 8 sucks back to vista !

[/scarism]

i wouldnt be suprised to see all those bashing in upcoming years :rolleyes:

[Julius Caro]

LOL...This guy is so full of it. Windows 7 is still in diapers and this guy is already talking about Windows 8 and 9!....LOL

Don't you think Microsoft already has enough problems as it is with Vista?

Windows 8 won't be around for another 6 or 7 years so chill out.

Didnt that happen with XP? XP wasn't even released and the names Longhorn and Blackcomb were already there. All they're doing is chosing the code-name anyway.

Even if it's not real (which is likely), it's not like it's critical information, the codename of a OS, lol. A full rewrite, now that's unlikely. Even if they did, it would take years to iron it out, so they would have to start doing it today if they wanted it to be "complete" by windows9

[Tech God]

I'm loling so hard right now.... building an os kernel in C#? ROFL IRL. not to mention the fact that C# can't directly control hardware, good luck writing a bootloader. You can't even write a bootloader in C (next best thing to assembly), that has to be done in assembly, so how the hell can you do it in C# LOL.

tell that to osdev.net

[Rudy]

I'm loling so hard right now.... building an os kernel in C#? ROFL IRL. not to mention the fact that C# can't directly control hardware, good luck writing a bootloader. You can't even write a bootloader in C (next best thing to assembly), that has to be done in assembly, so how the hell can you do it in C# LOL.

tell that to osdev.net

yes the kernel in singularity is in C#, C# can be compiled to a native binary too. The kernel is not 100% C# (95% C# and 5% C)

[y_notm]

I'm loling so hard right now.... building an os kernel in C#? ROFL IRL. not to mention the fact that C# can't directly control hardware, good luck writing a bootloader. You can't even write a bootloader in C (next best thing to assembly), that has to be done in assembly, so how the hell can you do it in C# LOL.

tell that to osdev.net

http://research.microsoft.com/os/singularity/

Not that I'm saying I believe the drivel in the first post, just that its possible (to a point)

[+Warwagon MVC]

Ya totally fake.

Even now companies are holding off on developing for vista for windows 7. But then if in the distance they say... well in Windows 8 uh good by NT, wouldn't you think they would rather wait for that.

[eein]

BS. It is not possible to build an O/S kernel using interpreted code in a language such as C# or F#. Complete and utter fake.

Maybe they wanna a new idea to OS. such as a virtual machine coming reality.

[Sranshaft]

If, and I do stress 'if', Microsoft is planning on rewriting thier OS from the ground up and have it ready for Windows 8 or 9, don't you think they'd start now and not wait the 2-3 years for Windows 7 to come out? Some truth to it maybe but as it's only a rumor well...

[Crazysah]

Ya totally fake.

Even now companies are holding off on developing for vista for windows 7. But then if in the distance they say... well in Windows 8 uh good by NT, wouldn't you think they would rather wait for that.

Yeah totally. But if Windows 8 comes much later then I think they will develop for Windows 7 as it is similar to Vista.

[TonyLock]

I also heard they are working on a desktop version of PHP called "PHP#". Should be interesting...

[let_slip]

Goodbye, XP. Hello, Midori

http://blogs.zdnet.com/microsoft/?p=1466

Might Microsoft?s Midori be ?Cairo? revisited?

http://blogs.zdnet.com/microsoft/?p=1473

[hamamo]

this is alot

[NelsonC]

I'm loling so hard right now.... building an os kernel in C#? ROFL IRL. not to mention the fact that C# can't directly control hardware, good luck writing a bootloader. You can't even write a bootloader in C (next best thing to assembly), that has to be done in assembly, so how the hell can you do it in C# LOL.

tell that to osdev.net

This is not true, C# has built in support for unsafe code via a compiler keyword which allows pointers to be used (important for access directly to regions of memory).

At the end of the day, most kernels consist of high level language + assembly. C# can do everything C/C++ can do, and it is still backed by assembly stubs (Or even inline assembly via crafty delegates) to execute the ring 0 instructions.

The C# code is directly compiled to x86 instructions, as opposed to JITed and cached.

Now, you may ask why this has an advantage over C/C++? Well C# code (assuming you minimize unsafe code usage, which is possible for 90% of the kernel) can be "proofed" or guaranteed to be safe (it wont be vulnerable to buffer overflows or memory corruption of any kind).

Why is this important? Well, when you can make inherent assumptions about the status of a piece of code in software, you can remove the hardware restrictions on it. So instead of having applications and services run in Ring3, they can all run in Ring0 since they are guaranteed to never touch each others address spaces -- or more importantly the kernel's address space.

This essentially means that message passing IPC is zero-copy, making it much better than shared memory mapping while negating the performance hit. This results in an extremely resilient kernel, which has the advantages of a microkernel without the inherent performance hit.

You see, in a normal situation (Monolithic, like the NT Kernel) applications run in a different processor privilege level called Ring3. However, this means that there are heavy performance hits in frequent context switches, to alleviate the issue most systems share mapped memory -- but that's also prone to corruption.

For more information, you can read some papers on Software Isolation and Channel-based Communication. Another interesting read, is the ability to selectively use hardware sandboxing to enforce virtual-machine'd native code. (Useful for example, for win32 backwards compatability).

I guess the point I'm getting at, is that all of this is very feasible from an engineering standpoint. Singularity paved the road for a lot of exciting changes in how Operating Systems are approached. Everything in Singularity is a good idea, and one can only pray that even one of the features in Singularity make it to any iteration of Windows.

Cheers.