Slashdot Mirror
How The Web Was Almost Won
radiator wrote to us with the latest writing from Tim O'Reilly, currently running on Salon. Tim, as always, does a great job writing, this time dealing with the Microsoft trial, the server market, and how close we really came to an Internet ruled by Microsoft.
It's irrelevant what MS stuff comes with NT. Obviously you get the good stuff if you pay the big bucks -- that's always true.
The issue is that MS required you to effectively pay for their product in order to be able to use another product.
In other words, they realized that NT Workstation was much too viable a server platform using 3rd party daemons, and changed the license to make sure you were paying for the MS daemons. That's way more insidious than the bullshit about including a browser in the operating system -- clearly the webserver is not part of the OS here, but if you're going to use anybody's, you've got to pay for MS's.
I'm not sure if I consider that unethical or illegal. It doesn't really matter. No company is going to put up with that -- it's too direct an example of the Free software rationale: if you buy it from one vendor, that vendor can screw you. This has been demonstrated time and time again in the computer industry, starting with the original "renters" of mainframe technology in the 60s.
I could not in good faith recommend a completely proprietary system (i.e. one which could not be replaced by an equivalent system provided by another vendor if necessary) today. It's too dangerous -- no company should be willing to take that risk.
[Argl, I mis-posted the first. Anyway, as Lando Calrissian said, here goes nothing.]
One simple way for Microsoft to change and break Apache's dominance of the web server market is to introduce 'feature creep' with IIS and NT, by integrating new features into the OS and IIS that aren't accessible to other servers.
An example was given with intranet corporate web posting. Sharing files and documents over a corporate intranet is the way to go. Email exchange and document sharing can be made much easier if it's all simply accessible with just a few mouseclicks from your Win98 desktop.
Now, everybody will want to put his drafts and whitepapers online quickly - and hey, look, there's a button just for that in Office2002.
And it all integrates nicely with Win2k and IIS. Why run Apache, which doesn't support all those nifty features and makes it 'more difficult' for admins to install and run it? If the users clamor for it, they'll get it, right?
After all, having admins mess about with incompatible stuff will annoy the management - this is all productivity loss, remember? Can't we just go with The Standard?
That'll be the first step.
Then, how does all that integrate with the outside world? Of course everybody in the firm will be using IE6 or 7, since it came with the OS and servers, and supports all the funky features Word2002 and IIS offer, 'for enhanced productivity and ease-of-use'. After all, it's all in the name of innovation - and annoyingly enough, it would make many things easier. But back to our example.
To tie everything in with the outside world, the corporate VPN and WAN, we need for our servers to communicate with each other. For instance so the offices everywhere can share the same documents. And send corporate email back and forth. And all of that ties in nicely with Exchange2k and all other corporate network solutions. From MS. All run on Win2k, with MS databases at the end.
After the internal structures of a business work so nicely together, we'll want the customers to be able to co-operate with all this. So we're adding special features. IE has an market dominance, anyway, and it ties in with everything else we're running.
Oh, you don't run MS? We're sorry, but our web logs and in-depth market research have shown that 92% of our customers are from home and corporate environments, which in turn mostly run IE. I'm afraid we can't support niche systems, Sir. We don't have the time, you understand?
This is how the web will be won. Unless Mozilla, Navigator 5, Konqueror, and Apache manage to impose a client-side as well as the existing server-side architecture on the market - an architecture that MS won't be able to break.
Does anyone remember 'Chrome', MS proprietary web enhancements? Or ActiveX-only pages? Guess what - if MS manages to fight back in the server market, it'll flood it with proprietary tech that will be tied to its OS, its servers, and its browsers. And then it will be all over.
So don't stand around idly, but go over to the Konqueror and Mozilla pages, and contribute. Even non-coders can write man and help pages and contribute to design decisions. Even you can add bug reports. Everybody can help - but as long as the infighting and holy wars continue, MS can only win.
And do you really want to see the message
Sorry, only for MS-enhanced browsers
on your screen? They can win it, and they will win it from the server side. We're already retreating in mass from the client side. Tim O'Reilly isn't an idiot, and he isn't a firebrand - he makes valid points: The entire MS case, and the FoF will be utterly pointless if the market decides to vote for MS servers in the end.
Apologies if this sounds inflammatory - I don't advocate that all MS products are bad, some of their software is awesome - but the way they market things goes against everything I believe in.
Alex
"Your telnet is talking to itself. Welcome to the wacky world of TCP/IP."
This could be the future for all of you radical non-Microsoft web users out there.
"Slapping people is fun." - Starla Grady