Slashdot Mirror
Microsoft's New Core OS Team Learning from Linux
sokk writes "Seems like Microsoft is paying attention to the Linux way of doing things. According to itworld.com, a new central engineering division will work on the core of Windows: "The Windows Core Operating System Division (COSD), within the company's Platforms Group, will be responsible for the core OS platform, including development, program management and testing, Microsoft said in a statement sent via e-mail.". A little further down the page analyst Rob Enderle: "They have been studying Linux extensively. Part of their study has been on how Linux has been able to maintain a high level of consistency in the kernel while groups around it maintain maximum flexibility,".
"
Microsoft is going to become more centralized to better compete with a competitor based highly distributed, decentralized development.
I'm amused, of course the proof will be in the bits.
Linux is Linux, if One need clarify their dist: <Dist>/GNU Linux
bsds are of course just BSD
According to the Microsoft apologists and mr Gates himself there is no innovation in Linux...
Soon to come: a new development process invented by and patented by Microsoft.
"Part of their study has been on how Linux has been able to maintain a high level of consistency in the kernel while groups around it maintain maximum flexibility,"
MS, here's a clue: Stop using undocumented/proprietary hooks into your OS from your apps.
Linux is the way it is (in reference to the above quote) because people stick to the "API"... partly because there's no other way, but that's another topic/philosophy alltogether.
- Preferences: Solaris 10 (servers), Ubuntu (desktops), Solaris 11 (personal servers) -
Rob Enderle makes more media pronouncements than just about any other analyst. In general he has no expertise and no information on which to base his statements.
I would completely discount any report that uses him as a source.
Don't take my word for it. Use Google and judge his veracity and competence for yourself.
Windows coders are not allowed to get anywhere near linux (or any other code). If a win coder needs to use a linux box, it will have absolutely NO source code on there anywhere. Code contamination scares the hell out of ms becasue if they end up with contaminated code the will be liable for huge amounts in damages and need to rework a large portion of windows(cause everything is intentionally over-integrated) in order to replace the offending code.
Shooting from the hip I'm taking this guess at the model for M$ future:
After WWII, Japan (well, Asia et.al.) learned to imitate US technology - we even helped them! Autos, Electronics, Watches and Cameras are prime examples.
The thing to watch for is what happened next - after Imitation came Innovation...and the popularity of those commodities took a swing to the East. The US economy took a pretty good hit, as I recall!
This is a wake-up call for Linux devs to stay sharp and keep up the steam of progress.
db
Cig:
ôô
It might also be due to Linux Kernel developers not being directly controllable by other areas of development (i.e. projects). For example with the mingling in Win95 of Explorer and the Kernel, for usability and not considering the consequences of such a decision.
Or the fact that the core team for the kernel is quite small and the direction of the kernel is ultimately controlled by this group.
This is likely to be an attempt to minimise the undue influence other departments have over the Windows Kernel development team. This being a good thing as it tries to prevent the projects goals being unduly subverted to make another projects life easier.
They didn't state that this was a kernel development team, though the name implies that the kernel will be part of their responsibilities. The core OS could include quite a bit more than the kernel. Kernel mode alone, in the diagram of the Longhorn OS, includes the kernel, HAL, device drivers, protocols (TCP, IPSEC, etc), portions of the storage and transaction systems, part of the DirectX graphics and audio drivers, input manager, memory, power, config, and process managers, plug and play, LPC, and so on. The 'Base Operating System Services' which includes the kernel mode portions also includes the window manager, GDI/GDI+, Direct3D, the CLR, and more of the storage and transactions subsystems. On top of all of that is the crap that's gotten the most attention recently, including Avalon, Indigo, WinFS, and the network class library (which might also be part of the Base OS services, it's hard to tell in the diagram).
Another thing that could be an explanation of this would be reaction to the antitrust cases not only at the federal level, but also from many of the states. If the Core OS is being developed by a seperate group, they could try to hold this up as an example of isolating the OS and API development from the application development, even within Microsoft itself. Of course, that also could backfire on them with any future efforts along the lines of IE and WMP, because they'd have to put more planning into integrating the needed features into the core OS before slapping together another product.
-PainKilleR-[CE]