Why copy Microsoft?
Summary: In a previous blog entry, I talked about why I thought Microsoft wouldn't have trouble convincing Windows users to upgrade to Longhorn. As I also claimed that older versions of Windows are the biggest competitor to Longhorn, the Talkbacks started discussing Linux, believed by many to be a credible alternative to Windows.
In a previous blog entry, I talked about why I thought Microsoft wouldn't have trouble convincing Windows users to upgrade to Longhorn. As I also claimed that older versions of Windows are the biggest competitor to Longhorn, the Talkbacks started discussing Linux, believed by many to be a credible alternative to Windows.
I argued in the Talkbacks that the only way that Linux would have a chance of being a credible alternative was if they worked harder at co-opting Windows technology. For ideological reasons, however, there was no interest in doing that, so I doubted Linux would make much of a dent. As someone rightly asked, though, why would Linux want to emulate Windows?
It's not a matter of whether Linux, or the Mac for that matter, should emulate Windows. They don't have to be Windows to compete.
Rather, they should endeavor as much as possible to make it easy for Windows developers to target their platform. The reason is simple: Windows is a standard, however de facto, and asking all those Windows programmers to reorient themselves around a Unix-based platform (or a hybrid one like the Mac) is like asking French people to start speaking English.
In fact, that's a good analogy, because think about all the support infrastructure that centers around the language spoken by the inhabitants of a particular region. If the French were to suddenly give up the language of their ancestors in favor of English, all the road signs would have to change, all the documentation on packaging would have to change, all official documents would have to be translated, bookstores would have to throw out all their old books and replace them with English ones, etc., etc., etc. In short, it would be a massive, and extremely costly, undertaking.
The same applies to shifting from Windows to Linux. Windows and Unix-family OSes live in two different programming domains. Granted, they have similarities, as do English and French, but I would hesitate to say that a Windows programmer could shift into the Unix world without any difficulties (and vice-versa). There's plenty of evidence of that difficulty. Though Linux fans hate to admit it, it's fairly clear that Linux growth on the server side has mostly been at the expense of the traditional Unices. I would argue that this is because it is so much easier to shift from Unix to Linux, and harder to shift from Windows to a Unix-family operating system.
This isn't about which platform is better or worse for development. I have my opinions, and so do you. It's about cold, hard cash, and the fact that whole industries spend billions on a particular standard (however de facto) and there is expense in shifting from that.
Of course, some will point out that there are large swathes of the world just starting to dip their toe into the IT waters. Developing economies have less of an installed base, and thus incur less costs in choosing an alternative platform. What's to prevent them from choosing Linux?
More on that to come.
Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.
Talkback
Windows programmers would have to learn how to code
We know which language is correct.
It's a shock when standard library functions in properly standardised language don't behave like bastardised Windows functions.
Yes, and it's a shock when a French person arrives in the US and finds that... almost no one speaks French! French is perfectly standard, and anyone who does not speak French has a lifetime habit of error to break.
When someone from the US arrives in France, he almost invariably has a moment when he realizes that someone has listened to what he said in English and not been understood. So he speaks LOUDER and slowly. Then finishes speaking looking at his auditeur with concern and doubt.
Suddenly, a whole new world has opened up, and it is not entirely a pleasant place. People do so many things just plain wrongly.
Sounds like you've been the discomfitted tourist in the land of Windows.
I'd picture it more like english slang
Or we could look at the other side of the argument. Maybe Microsoft is just today language and the standard is like old english, the type you see when you read Shakespear. Shakespear is difficult to read at best though it do use the proper language.
What is the "proper language"?
If each provides the proper language in its realm, then both are proper languages.
Is Unix a realm? Yes. Has Microsoft created a realm? Yes.
When in Rome...
I think you nailed it
That suits it well.
Windows isn't a realm.
I don't think a Frenchman would be surprised...
Americans, on the other hand, usually are. Most of them are convinced that somehow the rest of the world speaks English.
That may be because...
And all of that matters in what way?
Windows is NOT a standard!
So Bit: where is active directory or the mmc on linux? Why can't I run ms defrag on OSX? Where is IE for OSX, or Solaris? Can I run WMP on BSD? But doesn't a standard apply to *ALL* computing environments, say, like something such as TCP/IP, instead of Microsoft-only or mostly Microsoft-only environments?
[i]"Windows is the standard in the [b]dsesktop[/b] PC world.[/i]
Now THAT'S more like it! Microsoft is only [i]slightly more standardized[/i] on the desktop client side of the PC world. Nothing more. If Microsoft is the standard, then why is the internet run off mostly *nix/*nux boxes??? Why are more than 70% of all websites run off of Apache if IIS is the supposed standard? So the internet has been proprietary all along, and various engineers worldwide have all somehow worked together on proprietary formats to jointly create the Net as we have it today, even though it was really Microsoft all along that was the standard??? Pleeeeez. If Windows were any kind of a standard, then no coder would EVER encounter brick walls when trying to interface with it. There'd be no reason whatsoever for the EU to force Microsoft to open up their protocols, being that they're all standardized...right?
And why doesn't Microsoft run the big iron then? Why are company backends never pillared on Windows?
Windows is substandard. (nt)
Different Standards
Desktops....
More does not imply better.
You completely miss the point
Sure, you can write your hello world's in completely standard, cross-platform C/C++. But you CANNOT write a graphical Windows application of any usefulness using only standard, cross-platform code. You need to use Microsoft APIs (Windows, MFC, ATL, .NET, etc.) that, to my knowledge, have not been ported (even as wrappers to equivalent Linux API calls) to any flavour of Linux.
Java is simply not an option in many cases (esp. when you have hundreds of thousands of lines of perfectly good C++ code..)
Re: You completely miss the point
I think you don't have any idea what are you talking about... I hope you are not a programmer...
Why don't you tell us why you say that?
There are other libraries to draw from
I am not a programmer, yet even I know this.
Good answer
Proof
It's about the most compelling platform
It is already very hard for other OSs to compete against Windows due to Windows? great support of legacy Windows applications. But aside from this, MS is structuring Longhorn to be a next generation OS platform in which [url=http://msdn.microsoft.com/Longhorn/productinfo/conceptvid/default.aspx]developers will not only be able to create new eye popping, highly capable applications[/url]: MS also wants to ensure it can allow developers to do so relatively easily. It is very important to MS that developers can create very capable applications with relative ease on Longhorn: because if MS is successful at this, it will significantly decrease many of the economic reasons to even consider developing for other platforms. Why take 12 months to develop an application Linux or the Mac, when you can do more compelling work in about 3 months on Windows?