I don't think that's the point. We're talking about people running it from home, which likely means they really don't know what they're doing. Prior to IIS 6 (and Win98 was referenced so PWS/IIS 3/4(?) is fair game) this was a very big mistake since most everything got installed and left open by default. That's a huge gaping hole that non-pros don't have much chance of securing successfully. Apache installed without everything on, or even included, by default, so would have been a safer bet for those people.
No kidding, yet you're going to recommend Apache, instead, and leave them at the command line for configuration? Ridiculous.
Prior to IIS 6 (and Win98 was referenced so PWS/IIS 3/4(?) is fair game) this was a very big mistake since most everything got installed and left open by default.
What "most everything"? PWS hardly had anything other than a WWW publishing service to begin with. I shouldn't even waste my time trying to convince you, but recommending Apache for basic home users is a silly idea, both then and now.
Look at the Apache home page for it, not a single screen shot because it's all command line driven, yet you want to foist it on hapless home users just so you can look chic criticizing Microsoft:
Here’s some pictures of PWS management, graphically based and much simpler than Apache:
http://www.microsoft.com/technet/archive/pwebsrv/deploy/setuppws.mspx?mfr=true
I do see an FTP service there, but it is turned OFF by default:
http://www.coveryourasp.com/PWS6.asp
As is ASP page processing:
http://www.coveryourasp.com/PWS5.asp