Slashdot Mirror
Halloween Document Revisited
GroundBounce writes: "The front page of LWN has an interesting three-year-after analysis of the predictions in the Halloween document, which was "leaked" from Microsoft around Halloween of 1998. It's interesting to see how their predictions have/have not panned out."
As the memo says, they only way to "eliminate" OSS is to understand a process. Ironically enough, the entity searching for this "process" will in the end, find itself.
This is much like the ancient greek story OEdipus Rex, where he searches for a murderer and finds himself to be the person for whom he was searching. IMO, Microsoft in itself is the type of thing that drives OSS projects. The desire for non-corporate software, because of their greediness in terms of money, and inefficency of their products, and the desire to re-invent the wheel to be better than the current one, with input from all parties interested.
In order to combat the fees, the source code must be free and open, such that nobody will ever be able to claim it as their own and stop reproduction of it. And with OSS, anybody that sees a better way to do something, can contribute it. Whereas with the corporate model, you must write your programs to your manager's specifications, making innovation difficult at the developer level.
So in the end, the drive for OSS is to get away from the monolithic corporate model, which Microsoft ultimately represents. To destroy OSS, they must truly make their products more efficient and cause people to desire to migrate back to their software despite licensing fees.
Just some thoughts on the statments contained in the memo... maybe they're right, maybe they're not.
This reminder of halloween document more than shows us that the ONLY important remedy in the M$-DOJ case is to force open protocols and open data exchange formats. Everything else is just a bonus or bogus. Even restrictive OEM contracts would not uphold long, but proprietary protocols and data formats might have the potential to break neck to OSS development
If programs would be read like poetry, most programmers would be Vogons.
I can't remember where I read it (it might have been slashdot) but somebody recently was comparing Microsoft currently to IBM in it's last years of domination in the industry.
There are a lot of things in this article that support that theory too. Particularly Microsoft's concentration on proprietary protocols. Like the IBM of old Microsoft are trying to suck everything into their evil empire and proprietize (if that's a word) everything they can... including the internet.
Now, if I said to any Slashdot readers (and some preschool picture book readers) that I thought somebody could control the internet for their own benefit, and be truly successful at it you'd probably just point at me and laugh. And that would be quite fair I think. But not Microsoft. They're still trying to tame this internet thing.
You'd think after the success [sarcasm] of Push internet technology (remember active channels) and the microsoft network in it's original incarnation (now reduced to virtually an MS owned webring and AOL ripoff) and, speak of the devil; AOL's attempts to make the internet branded with AOL for anyone that uses it.
After all this has anyone ever come out on top of the internet? No. Of course there have been plenty of successes, but the internet still remains a global brand-name-independant network.
As the internet grows more it's that very size and reach that prevents it from becoming the MICROSOFT-InterNETWORK.
IMHO, this quest for making everything proprietary is just Microsoft going out of their way to piss people off. And much like the IBM keeping everything IBM attitude of past decades they risk screwing themselves royally because of it.
"How much truth can advertising buy?" - iNsuRge - AK47
Personally, I think that there has been a fundamental change in the marketplace during the last three years that Microsoft didn't anticipate. Three years ago, they were trying to figure out the best way to protect their interests from the likes of Linux and the rest of OSS. However, while they were concentrating on the external enemy, they missed the internal one. With Windows and Office 2K, Microsoft developed a product that is good enough for most people. That, combined with the subsequent major falloff in PC sales that accompanied the tech bust, meant that people had no reason to buy their software in the huge numbers they had previously been buying them in, and they certainly didn't see much need for further updates. Why pay for more software when what you have works. I would argue that OSS software is superior in most ways to CSS, but the simple fact is that most of Microsofts recent sales falloffs have not been attributable to OSS. Rather, we are seeing a general falloff in sales, mostly due to the fact that people don't need to buy more MS software. Thus, we have seen many of the recent (scared sh*tless) tactics that MS has been using. I'm sure Linux is still on Microsofts radar, but their real worry right now is how to get people to pay for something they really don't want or need, because their current business model is unsustainable long term. Therefore, they are making stupid moves that just serve to make people mad (licensing, Passport, copy protection). This is both good and bad news for Linux. It's good news because Linux has an opportunity to move in and usurp the reigning king. On the other hand, it could be very dangerous for OSS in general. There are few things deadlier than a cornered animal, and right now Microsoft has been backed into a pretty tight corner.
"If English was good enough for Jesus, it's good enough for everyone else."
It is true that closed-source projects can make one sort of deadline and stick to it. That's the "we'll ship by" sort of deadline. That's not the kind of deadline that knowledgeable users generally need.
The sort of deadline that open-source projects can generally meet is the "we'll get a nightly build up every night" and the "we won't call it version 1.0 until we're ready" sorts. These will do just fine for knowledgeable users. No closed-source company can meet this kind of commitment.
Notice that the one thing that for-profit, closed-source developers cannot do no matter how hard they try is ship bugfree software on a hard schedule. No one can. What they can do is ship version 1.0 when they said they would, and charge you for the service pack, and then charge you again when version 2.0 comes out with the features that you paid for in version 1.0 actually working.
Here's where the libre software is so wonderful. The total cost of ownership may be higher, lower or just the same as the closed source stuff, but the total benefits of ownership are generally much higher.
Folks like to say that you get what you pay for, and that's almost true: when you buy something you won't get any more than you pay for. The payment makes an upper bound on what you get. That isn't true when someone gives you something. The initial cost of $0.0 makes a lower bound on the value.
With libre software you get what the developers claim they're delivering, and sometimes a lot more. You don't have to wait for a deadline or an official release to start using the latest version of GNUfoo; you can keep trying it and start using it when you say it's ready.
Ask yourself: is it really an advantage for the closed-source companies to ship buggy crap that isn't ready, so they can meet a deadline? It is for them; it lets them gouge you and make a payroll. Is making a deadline that way really good for the customer?
See what I've been reading.
"Unfortunately, (emphasis mine) the story about Linux saving Amazon millions [cnet.com] was not as bad for Microsoft as it was good for Linux."
What is so unfortunate about something not being harmful to MS? Does harming MS somehow benefit others? Somehow a large, or at least very vocal part of the linux user base thinks so. I see the same feeling in the article:
"Reproducing what is available on a Microsoft desktop will win some users, but it is not enough. It may yet turn out, however, that Microsoft's licensing will provide that impetus to switch."
Now for the authors here, I can almost see a reason to want MS to lose market share. Their readership is made almost entirely of linux users and they are operating under the assumption that for there to be more linux users, there will have to be less MS users as if the number of potential computer users were a finite quantity of persons and organizations that will use MS *or* linux.
This assumption is just wrong. Number one, a majority of those who use linux on the desktop also use windows on desktop via dual booting or have multiple machines. Secondly, this is grounded on the notion that everyone who wants to use a computer for anything is already doing so and that the odd individual who purchases his/her first pc tomorrow will not possibly be a linux user. This might be the case for someone who heads to best buy and picks up a new system with winME preinstalled, but it neglects the guy who is first introduced to computers at his linux using friend's home or the second grader who browses her first website in a volunteer supported, linux based school computer lab. These are the people who will most likely stick with linux because after a few months becoming familiar with kde, mozilla, etc, they will have litle patience to "wait while windows builds a driver information database" or reboot for every "general protection fault in crappycode.dll"
Even so, this is only beneficial to people who make their money from a linux using market. As a user who loves linux and uses it almost exclusively, I don't care how many other linux users there are. I certainly don't feel like it's *unfortunate* when something doesn't hurt MS. I use linux becaues it does what I want it to, and as long as it meets that requirement I could care less what liscense the new MS product is released under or how many people buy their products.
The state is the great fiction by which everyone tries to live at the expense of everybody else. ~F. Bastiat
I don't have a link handy, but a while ago I read a very interesting essay where the author made the observation that the government doesn't have to legislate or force standards in order to affect a change. The government is such a large purchaser of computers and software that they could simply use their huge purchasing power to influence the market in the direction of open standards if they wanted to. If the government refused to buy into proprietary standards, many companies would support open standards rather than loose a customer that size.