Slashdot Mirror
Microsoft Trying To Appeal to the Unix Crowd?
DigDuality writes "With the news that Windows 2008 (recently discussed on Slashdot) will have GUI-less installs and be fully scriptable, that they've opened up their communication protocols for non-commercial usage and are providing a patent covenant (Redhat Responds), and now finally an interesting rumor floating around that Microsoft will be taking on GNU directly. Has Microsoft totally switched gears in how it is approaching the Unix and FOSS sector for direct competition? According to an anonymous email leaked from a Microsoft employee, it seems Microsoft will be developing a framework that will be completely GNU compatible. Microsoft CEO, Steve Ballmer, said on Friday (23 February) that they are aiming to restore a Unix-like environment to its former proprietary glory, at the same time proving that Microsoft is committed to interoperability. Ballmer emphasized that Microsoft's new strategy is to provide users with a complete package, and this includes users who like Unix environments. According to the supposedly leaked email, UNG, which stands for UNG's not GNU, is set to be released late 2009."
A rumour that sounds about as trustworthy as an e-mail from Nigeria.
A business tries to appeal to its market. The market changed. MS will change too. Its just long to shift gears of such a behemoth.
> UNG, which stands for UNG's not GNU
Wait is it april's fool's already?
Microsoft: Bringing new meaning to "Gnu's not unix"
Didya hear that there's this operating system that gives you the best of windows and linux? It's called linux!
There is already a book out on UNG. How do publishers knock this stuff out so quickly?
It's hard to believe that's how Micronians are made. Why don't we see it right now by having you both kiss one another?
And what is the difference between this and Windows Services for Unix? Sounds like rebranding to me.
"When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
If ever there were an appropriate story for the itsatrap tag, this is it.
First, build a language or system that runs existing programs.
Then change the compilers so they use MS-only, intel-only features by default
Then add attractive features at the source level.
Pretty soon, you can port *to* the new platform, but can't port away from it.
--dave
[PS: If you're already in that situation and want to port, send me private email]
davecb@spamcop.net
In the late 1970s and early 1980s MicroSoft sold a version of PC-UNIX called Xenix (they didnt write it). Until the mid-1990s PCs were too-weak to effectively run UNIX, so it was not a popular product. In the early 1980s MicroSoft decided to concentrate on MS-DOS and other products, so it sold Xenix to a company which eventually became SCO.
>Something like "Those who forget Unix are doomed to recode it".
And those who forget important quotes are condemned to reinvent them, poorly.
and has for a very long time.
The World Wide Web is dying. Soon, we shall have only the Internet.
since UNG is for non-commercial use only that mean business wont be able to use it... just jane & joe sixpack on his home PC...
Politics is Treachery, Religion is Brainwashing
Absolute power corrupts absolutely. indymedia
Let's see, the target audience could be :
* people who hate M$'s guts all ready
* Windows users who want to see what the fuss is all about
* Manager who read this and think "my tech people like Unix, I can buy this and they will be happy".
Would anyone reading this want to touch it with a 10' pole? Anyone curious enough to find out what 'faster and easier' features they've added?
This is gonna be a dog, a distorted bizarro unix.
Also, this idea reeks of embrace/extend/extinguish.
Palm trees and 8
They're opening up to "non-commercial use".
This isn't "Microsoft's answer to Open Source", it's "Microsoft's answer to shareware".
Releasing these documents is meaningless to the open source community so long as they require money for "commercial use". It's not meaningless, but it's not the open source community that will benefit.
My whole point of investing my time into Linux is because FOSS is a cultural phenomon that is completely new. Nobody, at least, not a single entity, owns Linux, and for that reason, it belongs to everyone. If you make some sort of a contribution to it, free of charge, it is almost like making a contribution directly to humanity.
I can't possibly see how Microsoft could pull off a similar thing.
No amount of being nice or slick marketing posters could make me think that writing for free on platform with a track record of sickening self interest could even remotely equate to the grand social experiment that is Linux.
But that's really not the worst of it. If anything, the slick marketing posters that come with Windows are a part of the problem. To a large extent, I view the drive for Linux as a push for a newer set of ethics for consulting firms.
We need to at some examine the relationship consulting firms have with large concerns like Microsoft. I always though that in the ideal case, a consultant was somewhat akin to a doctor, supposedly free of any sort of taint from any particular vendor's solution. But that's not what we have today. We have consulting firms that are "Junior, Gold", and more with Microsoft. It's an unholy alliance, where, consultants invest in MCSD's and other certifications, pay through the nose to get a product logo'd as compatible. In exchange, Microsoft gives those companies preferred listings and free development tools and operating systems. So basically, Microsoft is using artificial prices for copying to induce consultants to support their platform for free, and those consultants, in turn, are going to always be biased towards push their clients to Microsoft products. Indeed, higher levels of Microsoft partnership require sales of Microsoft products to achieve Gold or some other channel status.
If doctors did that, they would be barred from practice, and I think this comingling of a vendor with a solution provider is flat out wrong. In other lines of business, if you were paid by a vendor to advocate a particular product, selling everything from nuts and bolts to window frames, you would wind up in jail. But this practice of "partnering" is mysteriously ok in IT.
Adopting Linux removes this disgust. Because the software is free, there's no incentive to copy it, and ultimately, the customer is going to wind up with a solution that is genuinely more right sized for their needs. With Microsoft, you'll always have consultants pushing Biztalk and Enterprise this or Enterprise that, because, well, they are getting paid to do it.
The bottom line is this. If Microsoft genuinely wants to promote an open source environment, then yes, it has to make open source software, but it also has to work to promote the idea of a consultant as an independent advocate for his or her clients. We are not some salesman on the cheap motivated by free licensing for products similar to what Linux gives you for free.
This is my sig.
Microsoft would have to do a complete make-over on BSD the way Apple did with OSX. It's not that they couldn't do it, it's that they wouldn't. It would upset all of their development users to no end. There are so many developers making their products and living based on the Windows API that to move to something GNU "compatible" would simply be catastrophic in so many ways that I'd prefer not to put brain power into imagining the details. It would be ugly though... very ugly.
And in the end, it's not only that the Windows platform isn't and will never be efficient and reliable, it's that people who aren't using Microsoft as their basis for development or operations aren't doing so because they haven't heard or or tried Microsoft's stuff, it's because they have! Microsoft's reputation remains fresh in the minds of those who have rejected them.
To pull this off would require a lot. The first thing they would need to do is assure their developers that all the work, the time and resources devoted to Microsoft's platforms will not be wasted. To keep those developers would be no easy task. A large portion of them are 'worshipers' but many more are simply very invested in the current API and only take changes in small increments.
So such a move would take a long time -- even more than 5 years, possibly more than 10 -- to accomplish and even then, people are already burned on Microsoft's name, brand, style and attitude that it would take a long time to 'heal.' But 10 years is a long time to heal those memories, but why should the industry wait 10 years for what it has available to it now just so it could get something from a company that has a general strangle-hold on the IT market? People will figure it out eventually.
And since so much of today's business mentality is short-term anyway what with having to give in to short-term investors' demands or fear being sued, any planning more than 2 or 3 years out is just unimaginable.
Can they do it? Should they do it? Yes and yes! I have been saying it all along that if Microsoft wants to restore its former glory, it will have to dump the Windows API and either create a new, more stable and secure basis or adopt BSD and tweak it the way Apple did and hen create a WindowsAPI compatibility layer that actually works. Apple did it with their "Classic" mode (it's not perfect, but it worked well enough for many, and from what I hear Vista is a 'resounding success' even with its declining level of backward compatibility). Microsoft can do it too.
But will they? Not while present management is currently in control of things. If Microsoft wants another shot at being fresh, new and what's hip the way they were quite a few years ago, they'll have to dump their 80's-mentality leadership and fast! Only then will spurned anti-Microsoft people give a second look at Microsoft now or in the future.
"able to count on some excellent tools" and from one of the parent posts "Microsoft would never have been happy about it because it would further erode their lock-in."
... like some excellent tools. That way, you get some good and free applications, sitting on top of your proprietary OS. Plus maybe even help remove, some of the reasons some corporate (non-technical) bosses of companies would think their staff would want Linux. "Why both, its got the same apps on Vista?".
also from the article link http://www.royalidea.com/site/?q=node/12 we get this section...
"The aim of UNG is to write complete GNU-like tools and frameworks that will be completely compatible with existing GNU software and standards. These tools will run natively on Vista. This means that software written for the GNU environment will be able to compile and run on Vista with little or no modifications. Major software currently running on GNU/Linux will be able to run natively on Vista."
Microsoft's strategy revolves around the idea of lock in. Looking at this from the point of view of lock in, it then sounds like Microsoft is trying to find a way to get GNU code over onto Vista. If you can't beat them, then assimilate anything useful they have
While Microsoft controls the OS, they hold the foundations upon which all their competitors try to build a living. They are not going to give that up, but any company switching to Linux is a problem for them. So this is another chess move to try to reduce corporate customers moving towards Linux. Loosing corporate customers is what Microsoft really fears. Big customers moving away from Windows sends out a message to other big customers to act in a similar way. Microsoft wants to prevent this slide, especially as more cheaper embedded systems are very likely in the near future and a lot of them are likely to be using Linux.
e.g. News such as 10 billion ARM CPU sales isn't going to help Microsoft as much as its going to help grow Linux support, as a lot of ARM CPUs are using embedded Linux. Add to this the number of other CPUs using embedded forms of Linux, then industry support for Linux is growing faster than just on desktop machines. Microsoft needs to move to either block or reduce this, to help maintain their OS lock-in.
e.g. http://www.vnunet.com/vnunet/news/2207797/arm-hits-billion-processor
There are 10 kinds of people in the world... those who understand binary and those who don't.
I agree but I feel that in the long run it's going to totally destroy their lock-in. Let's say your a developer out to make some new software. Since *nix code can now run on Windows, OS X, Linux and Unix with a doable effort you might as well aim for that. Given a few years most software will be multi-platform and the idea of anything else will seem silly.
Note though that the GPL is specifically designed to prevent Embrace&Extend. They cannot take, say, gcc, and develop propietary closed-source extensions on top.Their only way of applying lock-in is by using propietary formats and protocols - which require apps to be written from scratch. So, nothing new on the assimilation front.
This sig does not contain any SCO code.
And say you're a company maintaining existing cross-platform software. Why pay the costs of maintaining Windows and Unix versions; just drop support for the Windows version, and let UNG pick up the slack. But once a few companies start doing that, the negative marketing consequences (not a real technical issue, just the *appearance* of loss of Windows support) will probably cause Microsoft to scuttle the whole idea and screw over everyone who had banked on it.
A better strategic approach would be the inverse - a Windows-compatible subsystem that runs on *nix. Then companies could drop support for their *nix versions, and let this subsystem pick up the cross-platform slack. This gives superior marketing optics - the major packages only appear to run on Windows. In reality, of course, it would mean that everything runs on *nix, but marketing trumps reality, so it would be a pyrrhic victory for the *nixers.
Win32 does not have a way to fork a process, but NT does. Passing a NULL image handle to NtCreateProcess() is similar to calling fork(), cloning the memory space as a new process. The NT kernel supports a lot of system calls that are not exposed through Win32, and it's a shame. The NT API is much more elegant and self-consistent than the Win32 wrapper, yet it's the officially undocumented one.
NT is almost a superset of the features of Linux. There are only a few concepts that don't exist in NT, like signals.
"Screw Sun, cross-platform will never work. Let's move on and steal the Java language." - Visual J++ Product Manager