Slashdot Mirror
Apache 2.0 vs. IIS
TonyG writes: "According to an item on InternetNews, the impending release of Apache 2.0 could very well mean the demise of IIS. Interestingly, the article asserts that Microsoft have already given up on IIS, the proof being its absence in XP Home and its non-standard presence in XP Pro. Apache.Net? Sounds catchy..." That's a silly argument by the internetnews.com writer - IIS isn't in the Home edition because Microsoft wants to charge more for "server" operating systems, not because they're "admitting defeat". But it's a decent look at the upcoming Apache 2.0.
Kudos for the apache team on 2.0 but until it's as easy to configure and add onto as IIS it will continue to be a battle with Microsoft.
It all depends. I'd say that for most situtions you are right - IIS is not only easier to set up, but it is a very fast web server (dynamic content). Apache, however, _can_ be easier to setup when you want to "script" say 500 small static sites. httpd.conf is not that difficult to learn, nor is it that hard to create a Perl or shell script to automate it. On the flipside, writing VBScript via ADSI to script IIS sites is a huge PITA (and performance hog). If MS would just move IIS's config out of the metabase and into some XML config file, then I think your statement would be correct accross the board.
There is no longer anything that can be done with computers that is nontrivial and clearly legal. -- Paul Phillips
It is incorrect to say MS has given up on IIS. XP Pro/Home are not meant to serve Web content they are meant for business or home users respectively.
.Net) will come in four different versions
.NET Web Server - for Web serving and hosting .NET Standard Server - for file and printer sharing etc. .NET Enterprise Server - for applications services, Web services .NET Datacenter Server .NET Web Server
The next server version of windows (Windows
Windows
Windows
Windows
Windows
Had MS given up on IIS they would have a seperate Windows
You have to admit that both IIS and Apache are both good webservers, its just that IIS gets a lot of flak for having holes in it that admins were not quick to patch, but at the same time Microsoft wasnt too quick on telling admins to patch it OR published it that broadly.. BUT IIS to some people is easier to use, so hence the easiness facto makes it attractive to a lot of people..
Apache on the other hand is also a good webserver, its been tested pretty throughly and doesnt seem to have that many holes, ( I cant say it does or doesnt because I havent looked ) but its also pretty intuitive to use for people that use Unix, so until the Unix population grows bigger than the windows population, IIS is going to be a tad more popular among that crowd..
I applaud microsoft for moving it out of the mainstream windows, it creates less of a hole to fix, and it decreases the risk of having another CodeRed type of thing happen again where users dont know that their computer is doing something.. but yeah, microsoft is tryign to make more money off it too.. this shouldnt surprise anybody
A missing piece in the acticle is the importance of Apache 2.0 for WebDAV. WebDAV is a HTTP-extension making the HTTP-server a real fileserver - Apache 2.0 comes with full WebDAV support. As WebDAV is quite flexible and allows stuff like meta-data, versioning and different authentication mechanisms (that are unfortunately not finalized yet) it is a possible successor for both NFS and SMB/Cifs.
WindowsXP supports the mounting of WebDAV shares, as does Linux with the help of the DAV filesystem driver. And Apache could be the standard fileserver... scary.
MS has always been successful in the enterprise space by focusing on developers and putting together a platform that creates compelling value for business software developers. While it's true that MS is rarely best at anything, it's one of a small number of companies that provides a complete, supported server product line (OS, DB, app server, web server, message queueing, transaction coordination, etc...) and a development environment that is reasonably integrated across it. Enterprises see this as an advantage.
IIS is perceived to be "good enough" by many companies and organizations. The effort to find, learn, integrate, and get support for another slightly-better alternative just isn't worth it to them.
However, MS is taking a huge beating on the security issues, and if they loose that "good enough" image, there will be a crack for Apache to squeeze through. Don't count on it being there for long...
I love it!
:)
"Microsoft has seemingly acknowledged defeat: IIS is not available on the Home edition of XP and the Professional edition, by default, is installed without IIS. "
Microsoft get's questioned as to why IIS would possibly be installed automatically, or why it would be installed on a machine whose user probably doesn't know what it is... So in an effort to offer a more secure platform they change the configuration in Windows XP. Home does not get IIS, and Pro only installs it by request.(Actually Win2k Pro only installed IIS by request as well, and WinMe didn't ship with IIS at all either, but whatever)
Now this guy claims it's because Microsoft is abandoning the market.
That has got to be the funniest thing I have read thus far this year. There are some equally stupid statements made elsewhere in the article, but it's really not worth the effort to point them out.
I'm sorry...but the person who wrote this article is very mistaken about the nature of IIS and Windows as a whole.
/. crowd has chosen to keep saying "IIS is installed by default" over and over during that time, basically in reference to NT 4 only--which, honestly, is a painfully old OS at this point in time.
First off, it's not in Home because...well...it's HOME EDITION. IIS is one of the major "features" in Professional compared to Home. You didn't see them putting IIS in WinME, did you? Didn't think so.
Second, I assume by "non-standard" he means that IIS isn't installed by default in WinXP Pro? Yeah. Time to wake up to the FUD that has perpetuated about the "default install" of IIS. Windows 2000, both Professional and Server, didn't install IIS by default either. IIS has been "optional" for almost 2 years now. Unfortunately, the general
I'm not going to claim that IIS has actually gained ground in the last few years, since I honestly can't be sure given all the conflicting reports. However, all MS's claimed increases have taken place without IIS installed by default on all current, shipping OS's. The fact that this will continue to be the case should have little to no bearing on their current position.
Now, a brand-new Apache coming out? That's news. Talk about that. There's really no need to toss in anti-MS propaganda at any possible opportunity because it just looks plain silly. (Although I'll probably be modded down for saying so.)
-Jayde
What's a sig?
IIS 6 (.Net Server) allows the metabase (where IIS keeps it's settings) to be stored in an XML file. You make a change to the XML file, it updates the metabase. You make a change to the metabase, it updates the XML file.
Very handy if you want to keep a standardised configuration backup.
This is one of the reasons why I rail against my company hiring consultants. If our experiences are a good metric, then I'd have to assume that most consultants are mega-'tards.
.00 CLASS IN HAWAII PLEASE!!!
Whenever we have hired consultants, they have given us products that range from mediocre to absolute crap. They have also been generally disinterested in providing after-hours support, even though they are paid for it. (Why should they be troubled at 3AM to fix something they wrote that's costing $5,000 for every minute it's broken? They're consultants. The company can do well or fail; it's no skin off their backs.)
Then, when they're long-gone, in-house types like me get a hold of their source code, SQL schema, etc. The source code is invariably coded in a style reminiscent of GW-BASIC (which, for those of you who don't know, is one of those crusty old BASIC interpreters from the mid-to-late '80s that make you use line numbers and have GOSUBs instead of functions): ultra-rigid structure, little to zero code re-use within the application, sloppy functions (if there even ARE functions), spaghetti-like style, etc. I recently looked at some utter crap left behind by a consultant. When I asked about it, I was told that someone had gone through a business requirements document with the consultant PARAGRAPH BY PARAGRAPH and just sort of threw together a hodgepodge of crap to handle it, rather than sitting down and actually thinking about how it should be programmed.
Oh yeah. The entire source listing was written with caps lock on, as was the SQL schema. BHRLHBLHRLHBLHGLHLGHRLHB!@@#@#$
So when I hear that consultants and other jerkoffs are allergic to text editors, it does not surprise me. OUGH NO!!! I HAVE TO COMPILE THE KERNEL OR APACHE!!! I'LL NEED YOU TO SIGN OFF ON THIS $5,000
Folks, if a total greenhorn (like I was a few years ago) can read a couple documents, figure out where httpd.conf lives, and tweak it (which any MORON could do, as heavily commented as it is), there is NO excuse for a so-called professional to shy away from it.
I will never - NEVER - be able to fully respect any system administrator, developer, or other technical-type IT worker who is not at least semi-proficient in some variety of UNIX (and by that I mean BSD as well as the SysV-based stuff like Linux and Solaris). It demonstrates lack of initiative and gullibility to Microsoft marketdroid drivel. In fact, if Microsoft didn't have world-class marketdroids, I probably wouldn't even be writing this paragraph. If you want to become an MCSE, more power to you, but UNIX aversion in someone who's supposed to be an IT professional strikes me the same way as a timid driver doing 15MPH up the onramp to the freeway.