Microsoft Trying To Appeal to the Unix Crowd? 468
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."
Wow (Score:5, Funny)
Re:Wow (Score:5, Insightful)
This is like Satan trying to appeal to Christians.
*nix users have already eaten the apple and realized they were duped.
If the Nigerian princes are right, I'd say it's time to sell your Microsoft stock.
Re:Wow (Score:5, Funny)
I think the analogy you're looking for is something more along the lines of selling sno-cones to Eskimos.
Re: (Score:3, Interesting)
Also, you left one other difference out:
Satan engages in questionable business practices.
Oh wait....
Re:Wow (Score:4, Funny)
Re: (Score:3, Interesting)
Marriage was supposed to be a contract, it became a government and religious institution. Prenups became an attempt to bring the contract part of things back into it.
Technically, if a woman cannot enter into a prenup (unwilling) it means she's likely to be taking you only for your money and goods and will fleece you dry. If she loves you, she wouldn't give a damn, so long as the prenup wasn't some ridiculous shitty deal. Marriage as it stands in its institutiona
Re: (Score:3, Funny)
Re: (Score:3, Funny)
Re:Wow (Score:5, Funny)
More like Yellow sno cones, being sold as lemon-aide.
Eskimo: Hey! This doesn't smell right!
Microsoft: Trust us, it's an improved lemon flavor.
Re:Wow (Score:4, Funny)
Re:Wow (Score:5, Funny)
[0] Unix
[1] GNU: Gnu's Not Unix
[2] UNG: Ung's Not Gnu
[3] UNU: Unu's Not Ung
[4] UNU: Unu's Not Unu
[...]
[n+0] UNU: Ununix's Not Unu
[n+1] UNU: Ugnu's gnot Ununix
[n+2] UNU: Unugnu's tong Ugnu
[n+3] UNU: Gnugnuung's gnongt Unugnu
[n+4] UNU: Ungnungnungnu[...]
Re:Wow (Score:5, Funny)
Re: (Score:3, Funny)
Re:Wow (Score:4, Funny)
Re:Wow (Score:5, Funny)
Re: (Score:3, Funny)
Gatesorade.
Re:Wow (Score:4, Funny)
Re:Wow (Score:5, Informative)
I am certainly not wedded to the command line in and of itself (though zsh is a tool I cannot live without), but I wouldn't be tempted even if they duplicate the Unix open architecture of interchangeable parts. I'm a Linux developer and user because I got extremely pissed off by having my system (the AT&T PC7300 aka the Unix PC) end-of-lifed on me and I never want that to happen again. Never. Those of you who love Microsoft Windows XP, take note. Maybe instead of complaining to Microsoft, you should join up with the ReactOS guys and keep the environment you love so much.
It worked for us
Re:Wow (Score:4, Funny)
The dice have decided- you get 'Insightful'. Congratulations.
Re:Wow (Score:5, Insightful)
Of course, these days Microsoft's lock-in is slipping away fast. More and more programs are showing up on the Mac, the web is going standards-compliant, and Java has ensured that Windows no longer locks customers in on the server side.
The way I see it, Microsoft is fighting. Which is step 3 of 4 in Ghandi's formula for success: "First they ignore you, then they laugh at you, then they fight you, then you win."
Re:Wow (Score:5, Insightful)
Re:Wow (Score:5, Informative)
There are still emulation libraries by Cygwin [cygwin.com] and MKS [mkssoftware.com]
Shell scripts are Microsofts weakness. Microsoft held off from including Monad [blogspot.com] into Vista for security fears. This was in a previous Slashdot discussion [slashdot.org]
Re: (Score:3, Interesting)
He did write the Emacs Operating System, after all.
IMO, that gets negative points, but it's certainly quite a bit far from nothing, you'll have to concede.
And you still have plenty of Unix options that don't involve free software. You just have to buy actual Unix.
Re:I think its great news! (Score:5, Insightful)
also from the article link http://www.royalidea.com/site/?q=node/12 [royalidea.com] 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 [vnunet.com]
Re:I think its great news! (Score:4, Insightful)
Re:I think its great news! (Score:5, Interesting)
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.
Re:I think its great news! (Score:5, Insightful)
Re: (Score:3, Interesting)
With Cygwin already around, and UNIX being open and readily able to be integrated into Windows, it would be a smart way to envelop potential UNIX users. Personally I'd like a Microsoft supported Cygwin, which isn't as buggy and doesn't feel as detached from Windows.
Re:Wow (Score:5, Informative)
I think Cygwin's full of too many hacks to be a good starting point. For instance, Windows programs have no ability to fork, and yet cygwin has a fork() implementation. Personally, I don't want GNU compatibility but POSIX compatibility. There are POSIX makefiles and there are GNU makefiles. The difference is that POSIX makefiles run everywhere, while GNU makefiles don't. Just the same, I try never use GNU-specific language features in gcc (I use -std=c89 or -std=c99 with -pedantic). GNU hinders interoperability, themselves. It would be good if a Microsoft-developed make (there is nmake, but I don't know how it works at all) had a POSIX mode and a GNU+POSIX mode, in the same way that GCC allows by use of -std=XXX -pedantic flags to disable GNU extensions.
Also, Microsoft's library model is positively nutty. Static libraries are stored as a big .lib file, while shared libraries are stored as a small .lib file together with a .dll file. Unix has .a and .so files, respectively. Inter-operable makefiles need simpler compilation systems than having three kinds of library files.
NT and forking (Score:5, Informative)
NT is almost a superset of the features of Linux. There are only a few concepts that don't exist in NT, like signals.
Re:Wow (Score:5, Informative)
As of Windows 2003 R2 and later, it's now called Subsystem for UNIX-Based Applications.
SFU/SUA applications are not Win32 applications; they operate on the POSIX layer. The apps are still Windows PE formatted binaries. Libraries are also PE and do not have a
The Unix environment is more Unix-like than Cygwin. Executables have no file extension; their names are all lowercase and appear that way in the Task Manager. SUA is aware of NT ACLs and permissions and appears to work with ACLs. It's possible to suspend and kill processes like any unix system.
SUA borrows a lot of stuff from BSD and includes some GNU code. Much of the userland is based on BSD; the SUA FTP application supports HTTP downloads as well, like NetBSD's IIRC. SUA applications can be compiled with the Microsoft Visual C++ compiler or the included gcc (version 3.3). SUA provides a
The userland is not as "complete" as a GNU system; commands like top and killall are missing, but ps and kill are functional.
Ports of some GNU software are available here [interix.com].
I haven't found much of a need for SFU/SUA, mainly because I typically have some sort of Linux system accessible and because PowerShell makes it possible to do many of the same things. But it doesn't feel too different than any other Unix
Here's the output of a few commands on my Windows Vista box:
Re: (Score:3, Funny)
Re:Wow (Score:4, Funny)
Re:Wow (Score:5, Insightful)
Re:Wow: Developers Developers Developers (Score:3, Interesting)
Even though the developer doesn't have the purchasing power, they do influence. If someone says, I need you to i
Re: (Score:3, Interesting)
Re: (Score:3, Interesting)
Re:Wow (Score:5, Interesting)
The NT kernel... is an interesting beast. There are a lot of things I really like about the architecture it presents. In many ways it has a lot of things that are more modern and better-designed than Unix-descendents (including Linux). At the same time MS seems to have made it more complicated than it "needs" to be, in part to satisfy backwards compatibility and in part because they just seemed to make some decisions I don't agree with.
Some of the good points:
1. Security. Yes, security. This is often brought up as a Windows problem, but that is largely because of policy decisions such as running as admin. (There are also a number of bugs caused by just plain bad coding that lead to buffer overflows. The biggest problem here in some sense is some of the abilities such as sending messages to other processes, which are probably too ingrained to pull out without some very clever modifications.) The security manager in NT provides a lot of very fine-grained control. Related, you don't need explicit file system support and a separate mechanism to do more than RWX on files. (ACLs are absolutely vital in some environments, and things like an "append only" or "create files but no delete" are useful for some applications.) In Unix, sometimes you use chmod, sometimes you use fsacl or whatever it is; the framework isn't unified.
2. Flexibility, in some sense. MS (in theory) can change the system calls that the NT kernel accepts on a whim. This is because all programs are dynamically linked to the Windows subsystem DLLs. These DLLs translate Windows API calls into whatever actual system calls they need. (One API call may generate zero, one, or more syscalls.) It's only the rare, "misbehaving" program that uses the syscall interface directly, and MS doesn't mind breaking them too much. (There are some mostly-legitimate reasons why you need to do this.) By contrast, statically linking code is a bigger tradition in Unix. (Then again, so is having source, so you can recompile if you change your syscall interface.) The idea of having various subsystems that provide different API views is pretty neat, though it's not a fundamental idea. (It's hard to say how it differs from just dynamically linking against just some shared lib.)
3. Not really a good advantage, but interesting and one of the rare examples of where Windows is actually simpler is in the read/write interface. In Unix, my impression is that if you are writing a driver, you "have" to implement to entry points for each: synchronous and asynchronous read, and synchronous and asynchronous write. In Windows, you only implement the asynchronous interface. If a synchronous request is issued, it is handled at a higher level and translated to an async call. (Upside: simpler driver code. Downside: inability to implement just the synchronous version.)
4. It's actually possible to use extended attributes on Windows, though admittedly only because of a huge hack introduced for a related but not-quite-the-same reason. (In Unix, opening a file with an extended attribute in Vi or Emacs, modifying it, and saving it is enough to kill the extended attributes. This makes them next to useless, when I at least can imagine a TON of very useful and neat things you could do with them if you could use them reliably.)
5. The registry gets a lot of hate, but I think a modified version could be better. There are a lot of very nice things it provides over config files. (Transactional access, fine-grained access controls (often nice for a corporate environment, at least in some sense),
6. Diversity. Yes, diversity. People often talk about the "Windows monoculture" on
Re: (Score:3, Informative)
Its a linux distro that runs on top of the NT kernel
Runs pretty fast, for what it's worth
Re: (Score:3, Informative)
Re:Wow (Score:5, Insightful)
What Gandhi left out is that, nine times out of ten, the fourth step is "then you're never heard from again".
Re:Wow (Score:5, Insightful)
Why would I bother (Score:3, Insightful)
Re:Wow (Score:5, Informative)
"Microsoft is looking at open-source software (OSS) as just another flavor of independent software vendors (ISV) software. Microsoft's goal is to convince OSS vendors to port their software to Windows. But Microsoft doesn't want OSS software to just sit on top of Windows; the company wants this software to be tied into the Windows ecosystem by integrating with Active Directory, Microsoft Office, Expression designer tools, System Center systems-management wares and SQL Server database.
In cases where customers and software vendors want/need Linux to still be part of the picture for some reason, Microsoft will suggest they use Hyper-V, its forthcoming virtualization hypervisor, to run Linux and Linux-dependent applications.
Microsoft's OSS strategy makes a lot of sense for Microsoft. It's another way for Microsoft to try to make Linux obsolete, and not look as obviously ruthless doing so. And for OSS vendors who are selling a lot of their software on Windows -- Ramji repeated a couple of times that more than 50 percent of JBoss' business these days is from software running on Windows -- Microsoft's OSS push isn't a bad deal, either.
Re:Wow (Score:5, Insightful)
Re:Wow (Score:5, Funny)
Re: (Score:3, Informative)
When I can recompile the Windows kernel to my liking, then we'll talk about how Windows will be a better FOSS platform.
Of course, you don't need to because it's not monolithic. The benefits of recompiling the linux kernel stem from the fact that everything in linux-land is jammed into the kernel.
You can simply load different drivers in pseudo-userland and run a separate set of services to completely rework your windows system. As far as enterprises and business customers are concerned, there's little to no benefit for them to be able to compile their own kernel unless it is completely monolithic- it's just a waste of time
Re: (Score:3, Informative)
Re: (Score:3, Insightful)
You mean, kind of like Linux's modules...? There's no reason to recompile a kernel just to get a system working these days, nor has there been since about 2001; indeed, vendors tend to recommend against doing so. But you do at least get the chance to say "no, I know what I'm doing" and choose.
Re: (Score:3, Informative)
Windows is absolutely monolithic. Even though you can dynamically extend it with drivers/kernel modules, it is still monolithic. As is Linux. When the module is inserted, it essentially becomes part of the operating system.
You are likely thinking of a Microkernel [wikipedia.org] architecture which separates services into completely independent components. However, the difference being if one component goes down, it does not take the entire system with it.
Re: (Score:3, Insightful)
But Microsoft doesn't want OSS software to just sit on top of Windows; the company wants this software to be tied into the Windows ecosystem by integrating with Active Directory, Microsoft Office, Expression designer tools, System Center systems-management wares and SQL Server database.
If this is indeed their strategy, then it's not a good one. If GNU tools are available on Windows, then it would only be a matter of time acceptable OSS alternatives appear that interwork with Active Directory or SQL Server clones. Hell, clone the interface, and use LDAP and Postgres behind the scenes.
Re:Wow (Score:4, Insightful)
Previously, Microsoft's fear was apps moving from Windows to OSS platforms. The fear was that if you could run your precious app on Linux, why keep Windows? Well, now they're talking about apps that started in the OSS world and trying to get people using them on Windows. That to me seems to be accurately fitting the hoary old gateway drug scare story! You dip your toe into OSS while still having all your comfy Windows apps on the box. You get to like the functionality, pretty soon the jump to Linux isn't all that abrupt, the desktop looks a little different but lookie here, all your apps are just fine.
By breaking down the barrier between Windows and OSS, Microsoft thinks Linux will lose the attractiveness and people will just run the OSS apps they like on Windows. I think it could accelerate the move the other direction. Well, wait five years and we'll see if I'm right.
Re:Wow (Score:4, Informative)
We're still waiting.
It's not like a Unix system, where a GUI is built on top of a CLI. Windows is GUI by design from the start. It's a whole different kettle of meat.
MS is a business (Score:5, Insightful)
Re: (Score:3, Insightful)
Yeah, I actually think that, in abstract, this sort of thing is very appropriate. Microsoft *should* be trying to appeal to the Unix/Linux crowd. They should be trying to make there stuff more interoperable, opening their protocols, giving headless servers, supporting GNU tools, etc. There's a case to be made for doing those sorts of things because of business interests, economic benefit, and technological need.
The only problem I see is that Microsoft has not earned people's trust that they'll do these t
Re: (Score:3, Interesting)
Microsoft is profitable because of Windows and without Windows they would be just another software company. Because they know Windows must continue to exist in its dominant and monopoly position, they must stop threats from dimin
Re: (Score:3, Informative)
All it means is that Windows (which btw, already has a partial, optional, Unix-like stack btw!) is going to offer more open source tools, more command-line utilities, more GUI-less fonctions, more open protocols.
Thats it. And thats been in the process for like ever (The latest version of Exchange for example, is fully administrated from Windows Powershell. The GUI works Unix-style, with a front end calling the CLI commands.).
Nothing more, nothing less.
Re:MS is a business (Score:5, Informative)
Cygwin is a solution, but of course, that has nothing to do with Microsoft.
Re:MS is a business (Score:5, Informative)
Re:MS is a business (Score:5, Interesting)
Actually, the proper term is WEIRDNIX.
For those not familiar with the term, WEIRDNIX was the POSIX crew's term for a hypothetical implementation that was technically compliant with all the POSIX standard, but implemented everything in the worst possible way. The idea was to find bugs in the POSIX standard that would allow implementers to claim compliance while violating the intent of the standard.
Mostly, people just sent in specs for a component that followed the standard but would in some way sabotage software that expected the obvious behavior. When NT came out, there were a number of discussions of its POSIX implementation, and a lot of people explained it by saying that Microsoft had done a full implementation of WEIRDNIX. Hardly anyone's POSIX software would run sanely on NT, and that was a simple, elegant explanation of why.
Is there any reason to expect things to be different this time around?
Re:MS is a business (Score:5, Informative)
Of course, their support hasn't been very good, but that has more to do with an unwillingness on Microsoft's part rather than any real technical reason. Typically Microsoft implements sub-standard support, then claims that their support is top notch. A few examples of this are the David Korn debacle:
http://slashdot.org/article.pl?sid=01/02/06/2030205 [slashdot.org]
Just as bad was the Kerberos debacle where Microsoft extended Kerberos for Windows [schneier.com] such that Unix machines could subscribe to a Windows domain, but a Windows machine could not subscribe to a Unix domain. I called a rep on it in one of their presentations on Win2K, and he assured me that I was mistaken.
Microsoft: UNG's not GNU (Score:5, Funny)
Wait is it april's fool's already?
Re:Microsoft: UNG's not GNU (Score:5, Funny)
Re: (Score:3, Funny)
Re: (Score:3, Funny)
Re: (Score:3, Insightful)
Then it seems to me, that perhaps, there is a very slight possibility that "UNG _is_ UNIX" ???
I guess that when the going gets weird, the weird go pro... (yes, that's a stolen sig)
Re:Microsoft: UNG's not GNU (Score:5, Funny)
Figures.
this has to be fake (Score:2, Interesting)
Re:this has to be fake (Score:5, Informative)
Also, this idea reeks of embrace/extend/extinguish.
Obligatory Jokes (Score:5, Funny)
Didya hear that there's this operating system that gives you the best of windows and linux? It's called linux!
book about UNG (Score:5, Funny)
Re: (Score:2)
BTW, I love the author's name E.X.Tend who presumably co-writes with E.M.Brace
Race to the bottom (Score:2)
Re:Race to the bottom (Score:4, Insightful)
Windows Services for Unix (Score:4, Interesting)
Re:Windows Services for Unix (Score:5, Insightful)
Xenix (Score:3, Funny)
Will believe it when I see it (Score:3, Insightful)
Makes some sense (Score:2)
Something like "Those who forget Unix are doomed to recode it". So the last big OS vendor is finally coming around. Good.
As for involving GNU as part of their plans, of course it's a trap
Re: (Score:3, Informative)
Re:Makes some sense (Score:5, Funny)
And those who forget important quotes are condemned to reinvent them, poorly.
This could be a trap for OSS (Score:2)
my opinion (Score:2)
they are aiming to restore a Unix-like environment to its former propriety glory
The most glorious thing that I can remember about proprietary unix was the awesome pizza box cases [classiccmp.org]. I seriously have no idea why the PC "tower" caught on instead of that.
itsatrap (Score:5, Funny)
Embrace, Extend and Extinguish (Score:5, Insightful)
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]
MSFT used to be a UNIX vendor (Score:3, Informative)
Re:MSFT used to be a UNIX vendor (Score:5, Informative)
Around the mid eighties, Xenix was the most widely installed unix, due primarily to the cheapness of the hardware on which it ran. To say it wasn't popular just isn't true.
Also, MS never sold Xenix directly to customers, quoth Wikipedia:
"Microsoft did not sell Xenix directly to end users; instead, they licensed it to software OEMs such as Intel, Tandy, Altos and SCO, who then ported it to their own proprietary computer architectures. Microsoft Xenix originally ran on the PDP-11; the first port was for the Zilog Z8001 16-bit processor. Altos shipped a version for their Intel 8086 based computers early in 1982, Tandy Corporation shipped TRS-XENIX for their 68000-based systems in January 1983, and SCO released their port to the IBM PC in September 1983."
Re:MSFT used to be a UNIX vendor (Score:4, Informative)
Great old times..!! I remember I had a 80266 machine back then, 10 MHz (way faster than the original IBM PC-AT, but you could always press CTRL-ALT-minus to set it back to normal speed in case of incompatibilities).
Well, on my 80266 10MHz/640kb RAM I used to do the college work (Turbo Pascal, Turbo C, documentation) on PC-DOS. When I "discovered" Xenix-286, the same machine could run 4 virtual terminals on the console, I was able to edit, compile, run/test on three different terminals. If I made a mistake on C, I'd get a coredump, but the machine kept running. Also, I was able to enable my modem, so a classmate could also work on what I was doing.
Great times, 80266 machine, 640 KB ram, 40 MB Hard drive.
Then I met a lot of people that were using SCO Xenix/UNIX on 80386 class machines, doing all kind of things from running a BBS with 20+modems, or running the billing system of local companies from multiple RS-232 terminals in the late 80's, early 90's.
MS already has unattended scripted installs (Score:3, Informative)
Re: (Score:3, Funny)
non-commercial uses (Score:4, Insightful)
Re: (Score:3, Informative)
When commercial distros (and community distros used commercially, like Debian) can't implement
They have to by law (Score:5, Informative)
Who's the target? (Score:5, Insightful)
* 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 [wikipedia.org] unix.
They're NOT opening up to "open source" (Score:5, Insightful)
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.
It's the channel partnering, stupid. (Score:5, Interesting)
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.
I don't buy it and it wouldn't work anyway (Score:4, Interesting)
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.
Some supporting info (Score:3, Interesting)
I didn't accept the offers, but here is some free advice:
- Get rid of single letter drive names (you know, the eighties called,
- The directory separator is '/', As Seen On Unix and URLs.
- Reorganize the file system more like Unix/Linux, and maybe rename 'Program Files' to 'Applications', have a
- Ship every copy of the OS with an X server.
- And I still need a compliant shell and C compiler to support the holy invocation './configure && make && sudo make install'.
Re:...then the next morning Steve Jobs calls (agai (Score:3, Insightful)
...asking what you're going to give him in return for ripping off his plan that brought Apple back into technical leadership. :)
Apple could dare to do it, MS can't. Read the archive.org pages from OS X 10.0 period, people, their core customers (including professionals) _hated_ OS X. Apple could stand to all those flaming, loss of developers, advanced developers having to re-learn things. It really needs courage.
There are posts from people who are clearly technical saying "What the hell? Ship MacOS 10 already. This junk doesn't work at all!"
Apple is a company which can actually warn its _own_ core system parts to keep up with times
Re: (Score:3, Insightful)
My god, the Unix kernel isn't the be all end all of OSes. What is with this attitude that Unix was the best?
To paraphrase a quote, "Unix is the worst operating system, except for all the others."
There's a reason that Unix dominates so many different areas, from the smallest embedded systems to the largest supercomputers: it's very, very flexible, and gets out of your way. It doesn't straight-arm you into "my way or the highway" like most operating systems.