Posted on 01/25/2006 7:10:50 AM PST by ShadowAce
Welsome to Europe! We punish success!
not only punish success, but probably allow hackers even more info to attack windows.
I look at software the same way cryptologists look at encryption algorythms--they should both be open for inspection, but still be secure.
WTF?
A graduate of the UK school of blather, I suppose.
If you "make products compatible with Windows", that doesn't make you a "competitor".
People have been making "products compatible with Windows" for a long time without access to the source code for Windows.
"...they should both be open for inspection, but still be secure."
... and Beer should taste great and be less filling...
I can't even begin to imagine how difficult it will be to deal with Microsoft's code for Windows. The sheer volume will be almost impossible to deal with. Further, by this time, the code will be so full of kludges and inactive code that it's going to cause enormous confusion in anyone who tries to decipher it.
I went back a while ago and looked at the source code for one of my old Windows apps, thinking I might get back into the business and update the application. I wrote this thing myself, with no other programmers involved. It's been 10 years since I finished the last version.
After several hours of study, I decided that I'm definitely done with coding. At one time, I could go back into the code and work with it, but I knew it then like the back of my hand, and could keep virtually all of the variables and routines in my grasp.
Windows, since the first version, contains so much code, written by so many people and teams, that it's going to be impossible to comprehend. Microsoft isn't all that terrific about transparency in its code, and I've worked with some Microsoft-originated stuff. Further, their need to maintain backwards compatibility (all the Win 3.1 apps I wrote back in the 90s still run perfectly in XP) means that there is lots of old crap in the current versions.
Good luck!
Do you mean win32?
Yes, and no. The argument (for good or ill) is that Microsoft uses its dominant position in the operating systems market to unfairly compete against applications developers. Under most anti-trust laws, leveraging a dominant position in one area to stifle competition in another is illegal. The remedy in this particular case is to allow other applications developers access to the underlying Windows operating system source code so that they can compete on a level basis with applications written for the Windows OS.
Of course, the counter-argument is that it is only because of the applications that Microsoft enjoys a dominant OS position. Unfortunately for the folks in Redmond, that didn't help them in the EU case.
Since when is this about releasing code? I thought MS was only supposed to release full API specs to allow for compatibility. Forcing them to release code sounds quite anti-capitalist.
That's a good point. My guess is it's all about incrementalism. First the APIs, then the code. Pretty soon EU will force them to stop charging for access to the code as it discriminates against the small/individual developers.
In other news, the courts ordered Ford to turn over all schematics and blueprints to GM and Daimler-Chrysler in order to ensure all cars can drive on the same road.
All they have to do is buy one and take it apart.
Yeah, by bundling apps with the OS, such as Media Player and IE and so forth. So how does forcing open the source remedy bundling? Answer: it doesn't, obviously. It doesn't have a thing to do with the alleged crime. The EU is simply doing this because they can, and because there haven't been any operating systems of note to come out of Europe since...well, ever.
"Do you mean win32?"
Nope. All my windows apps were written for the 16-bit version of Windows. That they still run perfectly in XP, but were written for Windows 3.1 is amazing to me. There's no reason that XP should be expected to run 16-bit Windows software, but it does, and perfectly.
My software makes many calls to old .dll libraries. It also does stuff that is completely different in XP, such as font installation and getting font information. Yet, .dlls I wrote to do font stuff still work just fine.
It's amazing. And it's another example of why the XP source code is going to be virtually impossible to decipher for anyone not intimately involved in its creation.
"I suppose the next step would be for the EU courts to decide that Microsoft must also provide access to all the information explaining the code, and provide technical support to all the outside developers who can't figure it out."
It does not make you a competitor with widows but it can make you a competitor against MS. Think about it what if Apple wants to start selling their office suite on windows?
I'm not saying I agree with it, but there are two possible remedies (if you're going that route in the first place): 1) force Microsoft to stop bundling altogether or 2) make it easier for third-party vendors to provide alternatives to the bundled applications so that users may choose to make the switch for whatever reason.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.