[ale] Systemd rants (was bow head)

[Jerald Sheets]

I think that at some level, we’re dabbling in philosophy here.

For instance, one could argue that without any plugins, additions, and most simply configured that Apache is similarly “bare bones”.  (http_core.c and core.c only) certainly falls within this purview.

Apache at its simplest satisfies the description.
Nginx at its simplest satisfies the description.

It’s when vendors begin “front-loading” the applications with all sorts of modules and add-ons things start to get weird.

—jms



> On Sep 8, 2017, at 11:34 AM, Kyle Brieden <kyle at txmoose.com> wrote:
> 
> I would argue that Nginx is MUCH closer to the "Do one thing" philosophy than apache is.  Nginx essentially only serves up static content and caches some of that static content in memory to serve it faster.  I think that falls well within the "do one thing" of serving static content.  Nginx doesn't do any server side processing at all;  you need php-fpm for php, gunicorn/uwsgi for python, etc...  Nginx passes the request back to those, those do the processing and hand rendered pages to nginx, and as far as nginx is concerned, that's a static asset that it fires out the front.  All HTML/CSS/JS assets that it serves are static content, rendered in browser.  One could argue that nginx isn't a "webserver" at all, although that's what it made it's name on.  It basically only does proxy to other things that do processing and then serves up static objects.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP
URL: <http://mail.ale.org/pipermail/ale/attachments/20170908/30fae079/attachment.sig>