SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : How high will Microsoft fly? -- Ignore unavailable to you. Want to Upgrade?


To: Cameron Dorey who wrote (44919)5/18/2000 12:15:00 PM
From: SunSpot  Read Replies (1) | Respond to of 74651
 
Apache is not very interesting on NT, because an important parameter for Apache is cross-platform compatibility of a web-site. Apache on NT has many incompatible differences to other Apache implementations, like drive letters (C:) and backslashes (c:\windows).

And if you know how to do Apache, Linux or FreeBSD is the obvious choice for deployment.



To: Cameron Dorey who wrote (44919)5/18/2000 2:13:00 PM
From: JC Jaros  Read Replies (1) | Respond to of 74651
 
BTW, thanks for telling me about Netcraft ... --- You're welcome. --- As big an improvement that Win2k may be, the assertion that NT may have a larger web server market share would run radically against the trend. There's no escape from the Internet being a collection of Unix services. I think the days of people believing Bill Gates' promise to create a "better Unix than Unix" are long gone. --- The Internet runs on Unix and not VAX/VMS for a reason. Much of that reason is to do with the GUI being folded into the kernel. Windows is designed for an end user context. Unix wasn't. FWIW, a system administrator, unless he or she keeps the web server on the nightstand, is apt to chose Apache on *nix if for no other reason than remote admin. In the end, it's all about the architecture. Mac OS X includes FreeBSD for reasons beyond novelty (IMO). Speaking of FreeBSD (Bill Joy style 'Linux') it does MS Front Page extentions. When you talk about having support for MS programs, is that what you mean? --- You're right about the network being heterogeneous (something the M$ business plan wasn't/still isn't prepared for). It doesn't mean though that folks run Adobe Go Live on the same machine as the web server. At some point, you need to break out of the 'one machine does everything' PC precept. On the other hand, through a licensing agreement with AT&T (who has access to the Win32 codebase), Sun Microsystems is able to offer the most robust, scalable and generally ascended solution of availing Windows services on the enterprise (Solaris) server, but that's relatively high end. In the space you're talking about, I think, the typical configuration would involve the Samba program which makes Linux a pretty much invisible replacement for the Network Neighborhood (there goes the neighborhood). --- So, less and less is it about sucessfully sheilding the user from the machine with an idiot proof interface, especially when it's so easy for any idiot to gain 'super user permissions' and wreak massive havoc. --- Making the choice between running Apache/*nix or Apache/W2k is like an IQ test. :) -JCJ