Quake3World

seremtan wrote:yes, microsoft should pull out of one its biggest markets and lose a giant portion of its profits plus hand over a huge market share to someone else. it stands to reason

// © 1985 - 2003 Microsoft Corp.
// EXPLORER.EXE

int Main() {
  long wndMainProc;
  int prog_returnCode;

  while (1) {
    wndMainProc = wnd->getProccess();

   if (wndMainProc == 0x00000F && prog_returnCoed) // TODO: check spelling after lunch?
     break;
  }
}

seremtan wrote:yes, microsoft should pull out of one its biggest markets and lose a giant portion of its profits plus hand over a huge market share to someone else. it stands to reason

+JuggerNaut+ wrote:instead of giving up intellectual property? maybe. :purpledorkface:

Tormentius wrote:

seremtan wrote:yes, microsoft should pull out of one its biggest markets and lose a giant portion of its profits plus hand over a huge market share to someone else. it stands to reason

I'd say that's less costly than giving up the source code they have poured countless billions into developing so that it can become a free-for-all. There is abso-fucking-lutely no reason that they should be forced into going open source. MS needs to take a stand IMO. Glossy is right as it's by far the most known product, especially for home users, but that doesn't give the government(s) a right to place unreasonable expectations on MS as a company.

This is a shining example of how government and buereaucrats don't have the faintest idea about technology yet think they can regulate it anyways.

seremtan wrote:

+JuggerNaut+ wrote:instead of giving up intellectual property? maybe. :purpledorkface:

it's not like they're not being asked to make the entire source available on kazaa or anything

the media player thing doesn't sound unreasonable. i mean, people can still d/l it from microsoft anyway

i'll admit i'm not really au fait with the API thing...

R00k wrote:This is Windows source code -- if it were made available to vendors it would be leaked eventually (parts of it at the very least) and all over the internet.

APIs are Application Programming Interfaces. They let developers write code to interact with pretty much every single aspect of Windows. You can write your own services with APIs, create your own branded Windows distributions, interact with networking protocols or even write your own, change the Windows interface any way you want, etc. etc - it's nearly limitless for all practical purposes. These are what even Microsoft's own developers use when they write applications for Windows. I've only done a moderate amount of programming for Windows, but I don't know of anything you can't do, aside from making changes to the kernel and other low-level things - but things like that would be changing the most fundamental aspects of the operating system, basically rewriting it your own way, and there are lots of very good reasons that cannot be done, not least of which being that Microsoft has the right to protect their intellectual property.

As an analogy, imagine someone invented a basketball-sized device that was able to produce nearly unlimited amounts of energy using water and steam. They sold this device on the market and it revolutionized the way people work. They created the device with fittings and plugs that would allow other inventors to use the energy in nearly unlimited different ways to create their own devices powered by it. People made climate control systems, power tools, ran entire city power grids off them, our manned space flights ran off them, nearly every new energy-consuming device in the world was able to run off of it. Thousands of new companies sprouted up because of the possibilities this device created, and it was so widely used that inventors could be made overnight millionaires by coming up with a new way to a fundamental and necessary task using the device.

Then imagine people became discontented with the fact that one person or company had the rights to this object and noone else knew how it worked. Sure, it was patented, but the very core concept powering it was a tightly-kept secret, and this device was used to operate the entire world's power systems. So people started getting the idea it wasn't fair for one company to have the power/control they have over everything, and started to complain to the government. They petition the government, and the government threatens to fine the creators of the device - unless they release their blueprints, allowing any person in the world to completely recreate the device in their own basement. And also in the process, allowing anyone to know the most closely-kept vulnerabilities of the device, making it susceptible to all sorts of attacks -- i.e., even people who are just on the same power grid with the device would be able to remotely damage it, make changes to it, or otherwise do what they want with it.

In other words, people become unhappy with simply being able to utilize all the power and possiblities created by this new device; they want more. They petition the politicians, who know nothing of the way the device works, convincing them that, without the blueprints for the device they cannot make competitive new tools that attach to it and run off its energy -- ignoring the fact that they are already doing exactly that, along with the rest of the world.

The company that invented the device has a huge, well-funded team that creates their own tools powered by the device, and since their name is recognized around the world and they have money to market their inventions, their tools are bought by the common consumer more than anyone else's. So even though they are using the exact same adapters, fittings and plugs for their inventions that everyone else is using, their products sell better, and since they have such a massive, well-funded team creating their new devices, they are high-quality products which utilize the energy output to its maximum potential. This adds fuel to the fire, and helps convince the politicians that something is probably amiss, so the politicians threaten to fine the company if they do not release their blueprints and trade secrets of the device.


The developers who are petitioning the EU Commission are either ignorant of some of the technologies they work with, or they are being disingenuous in their statements to the Commission, because they have access to the exact same tools that Microsoft uses, and interact with the operating system using the exact same adapters. Forcing Microsoft to release its source code to anyone based on these arguments which are fundamentally flawed to begin with, is completely ridiculous.

Foo wrote:
BTW on one hand it's being argued that people have full access to develop anything they like on top of the windows system, but it's simultaneously being argued that there's some hidden ways of working in this code which MS needs to protect. Which is it?

seremtan wrote:an alternate imaginary scenario might be: suppose someone had patented the secret of fire, and sued anyone who made their own fire, and insisted on being the sole provider of fire, arguing that people were free to use the heat energy of fire any way they liked. clearly legitimate questions would arise about whether that monopoly on the secret of fire was a good thing, even though the principle of property rights seemed to make the monopoly unassailable

it's an interesting conflict of values, which i don't think is a clear-cut as some are making out. i'd have to think about it more before deciding who i think has the right idea

Foo wrote:So what you're saying is that the pressure to do this has come from people who want to pirate Windows?

Foo wrote:I didn't want to weigh in on this argument, but it's really dumbbbbbbbbbb so suits me well.

BTW on one hand it's being argued that people have full access to develop anything they like on top of the windows system, but it's simultaneously being argued that there's some hidden ways of working in this code which MS needs to protect. Which is it?

seremtan wrote:ok, i hear what you're saying, and it sounds like what this boils down is distributed power/knowledge vs property rights

an alternate imaginary scenario might be: suppose someone had patented the secret of fire, and sued anyone who made their own fire, and insisted on being the sole provider of fire, arguing that people were free to use the heat energy of fire any way they liked. clearly legitimate questions would arise about whether that monopoly on the secret of fire was a good thing, even though the principle of property rights seemed to make the monopoly unassailable

it's an interesting conflict of values, which i don't think is a clear-cut as some are making out. i'd have to think about it more before deciding who i think has the right idea

R00k wrote:Well, Windows is not a naturally occurring phenomenon and it can't be "discovered;" in fact it takes a massive team of highly paid people to create it, so I don't think that's a fair analogy for the situation.

Foo wrote: APIs for Windows are only created for things MS wants to make available. They are not comprehensive, especially not when dealing with complex interaction with the OS, as is this example with the networking subsystems.

think it's perfectly acceptable to force them to a point where it's easy for their competition to be able to interoperate seamlessly. Microsoft is right that source code isn't required, however the commission is probably also right that Microsoft hasn't done enough to comply.

Foo wrote:My general point is that there's no big secrets to the way Windows works. All the individual features of the OS are things which many software manufacturers could recreate on an individual basis.

The main reason no big rival OS comes up with the same functionality as Windows is that there's no business big enough to put it all together.

Hence once that's understood, the question becomes why would anyone want access to parts of the Windows source?

Because on the finest levels, getting stuff to interact with Windows can be problematic, as anyone who's ever tried to reverse-engineer even a basic networking protocol would be well aware.

Timing loops and random delays where you dont know the random seed being used are but a few small examples of how, on the micro scale, not having direct access to the source can be a pain in the ass.

APIs for Windows are only created for things MS wants to make available. They are not comprehensive, especially not when dealing with complex interaction with the OS, as is this example with the networking subsystems.

Foo wrote:

R00k wrote:Well, Windows is not a naturally occurring phenomenon and it can't be "discovered;" in fact it takes a massive team of highly paid people to create it, so I don't think that's a fair analogy for the situation.

Neither is the creation of fire as performed by humans.

Windows is just electrons flowing which happens in nature too.

R00k wrote:So is everything in this world. By that logic, nothing in history would ever have been eligible for patent or copyright.

R00k wrote:You'll have to cite some specific examples where APIs are not sufficient to create complex interactions with the OS, because I do not believe that is the case.

Microsoft publishes white papers and documentation that is more extensive than that of any other software I've ever worked with, specifically tailored to help developers interact with their OS. As torm said, they also have partner and ISV programs that provide developers with custom solutions to help with any problems that they may not have been aware of before.

You can say a lot of things about Microsoft -- and I have -- but their assistance in helping people work with their products is outstanding, IMO.

It sounds like you may be approaching this from the point of view of independent, open-source developers (?). If so, I have a lot of respect for the open-source community, but I can't think of a reason they should be able to force commercial shops to open up software they've spent billions of dollars and years evolving and tuning. What incentive would any other companies have to create such products, if their intellectual property can be handed over to certain companies at the whim of legislators?

Foo wrote:I think this comment on the article got it down quite well:

think it's perfectly acceptable to force them to a point where it's easy for their competition to be able to interoperate seamlessly. Microsoft is right that source code isn't required, however the commission is probably also right that Microsoft hasn't done enough to comply.

Foo wrote:BTW aside from having windows applications work well with Windows, you dont think there's any legitimate reason to have microsoft competitors be able to improve cross-compatability with Windows?

Foo wrote:

R00k wrote:So is everything in this world. By that logic, nothing in history would ever have been eligible for patent or copyright.

I wasn't arguing that being natural excludes the notion of patent/copyright. But that shooting down the analogy on the basis of it being a natural phenomenon was but a non sequitur in an already complex debate.