Why I Hate the Apache Web Server 558
schon writes "Today's the last day of ApacheCon Europe; There was a hilarious presentation entitled 'Why I Hate the Apache Web Server' for anyone who has expressed frustration with the various inconsistencies and nuances of the Internet's favourite config file. And yes, it includes a comparison to Sendmail."
is this the internet ? (Score:1, Interesting)
PDF has no place on the Internet, thats why we use HTML , but that would interfere with Adobes buisness model
How to fund Apache improvements (Score:5, Interesting)
Apache is great but it could be *significantly* easier for beginning webmasters. And for companies to fund changes.
Re:Whoops (Score:2, Interesting)
Re:Those PDF's again... aaargh (Score:1, Interesting)
Winston Churchill (Score:2, Interesting)
"It has been said that democracy is the worst form of government except all the others that have been tried."
"It has been said that Apache is the worst web server except all the others that have been created"
There are some good reasons (Score:1, Interesting)
Posting anonymously so that no one will search back in history and see how badly I flame Apache when I'm trying to sell to customers who are basing their systems on Apache/PHP.
Re:Comic Sans is..... (Score:2, Interesting)
At some point, they figured out that whole "sound" deal, so 3DMM got voices, and the world got Comic Sans. (Sorry about that!)
I'm actually one of the leading programmers from the 3D Movie Maker Community (which still exists)... We're people celebrating a program that gave the world Comic Sans.
Aren't we bastards?
Start using Konq. (Score:3, Interesting)
It beats the shit out of Postscript files (I shouldn't have to install 5 separate packages for 1 file format!), and is highly preferable to a powerpoint doc on the other end of the hyper link (which I wouldn't be able to read anyways).
Re:There are some good reasons (Score:2, Interesting)
2. Try this. [caudium.net] Modules are Pike (similar to C++) objects. They can be reloaded on the fly, don't need to be compiled before they're used, and do not require a restart of the server.
3. Try this. [caudium.net] It supports threads just fine.
4. Try this. [caudium.net] Support for PHO (for those who want it) as well as a built-in dynamic page generating language (RXML) - as well as pike scripts (if you want more power.)
5. Try this. [caudium.net] Memory management is not an issue.
Caudium is a wonderful web server platform - it's faster, more powerful, and easier to use than Apache. Once you try it you won't go back.
AMEN BROTHER!!! (Score:2, Interesting)
So every time I start trying to hack together an Apache config file, then setup the .htaccess, and then...well, about that time I say awfuckit
and just grab one of those dusty old code nuggets
and roll my own. its actually faster to setup that way...and possibly more secure, since I hardwire the pages/images/etc.
Apache performance can't be beat ('cept maybe for the kernel-embedded HTTP server, can't recall the name), but the config process is way too damn difficult for something with such a simple protocol; hell, I can completely reconfig a UNIX kernel more reliably, and in less time, than configing Apache.
Re:Comic Sans is..... (Score:2, Interesting)
Re:Comic Sans is..... (Score:3, Interesting)
As a consultant (Score:3, Interesting)
Seriously though, for a lot of tasks these days I use the more lightweight thttpd [acme.com] daemon. Uber-simple config files, very low overhead, supports per-URL throttling out of the box. It's superb for image servers, or pretty much any application where you don't need dynamic pages - and believe me, there are still plenty of places you don't need dynamic code.
Re:General-purpose config file parsing (Score:2, Interesting)
I dislike the Windows registry because it is a mess.. It can be really hard to migrate settings for a specific application in Windows, whereas it is often easier in Mac OS X.
Of course, apache and all the other Unix-native apps on the Mac still use the painful configs.
Some more (Score:4, Interesting)
First, we have this [apache.org].
And a quote from the default config file: OK. So I'll define as follows: Then, we have this [w3.org].
OK, so I have some legacy documents, so I'll just define as follows in <HEAD>: And let's try it out... WTF?? It does not work! My browser thinks it is UTF-8.
Oh wait, it actually works, if I'll define this instead of that above: Brilliant! So if the AddDefaultCharset is defined in httpd.conf, the Content-Type encoding of the actual document must be defined in lowercase, or it'll be ingnored! Now, where the f*** this is documented??! Examples at w3.org specifically uses uppercase. Apache permits uppercase in httpd.conf.
Apache messed it up again.
Even the guy who designed it doesn't like it. (Score:2, Interesting)
Here is a, uh, rather ambivalent look at Comic Sans [connare.com] by its designer, Vincent Connare.
Apparently, he saw Times New Roman used as the font for speech balloons in Microsoft Bob, which he thought was a terrible misuse of the font. So he designed a new font, Comic Sans, for those speech balloons. From the article:
Re:Sigh. Just a half-witted rant, as I expected... (Score:3, Interesting)