Roughly 1/3 of the internet runs on httpd, but it seems like a lot of developers have no idea how to configure it, let alone remember it exists.

Having to explain what FastCGI is or basic httpd directives is something I feel like I’m doing more and more.

@dragonmantank that makes me feel each and every one of my years -- is this PHP folks or a wider developer community? Do you have any sense for what these folks are using instead? (nginx? or "i dunno we just add a container to the registry and stuff works"?, etc.?)

@alanstorm A wider audience, but much of it is the abstraction of services because of things like containers. "Stuff works when I launched the container" hits the nail on the head.

Case in point, was working with DevOps and had to explain that PHP frameworks don't govern what port we listen on, and that a real web server is needed. That launched into a discussion on (Fast)CGI + server config. Then because we were using httpd, discussing directives.

This was with people that do TS and golang.

@dragonmantank _nod_ -- I've run into two flavors of this -- "I'm a software engineer, other people figure out how to operationalize my code" and then folks from the Node.js/GoLang/other-language where you end up coding small web servers yourself every day.

Related: Back in my New Relic days I found myself having to explain (and justify?!) the FastCGI and mod_php split and apache extensions generally to a bunch of unimpressed C programmers and the vibe was pretty out there.

@alanstorm It's funny, because I remember when we hated others operationalizing our code due to sysadmins not understanding how to handle code bases.

The number of times people would get the wrong versions of PHP or MySQL, or outdated distros because "that's company policy/what do you mean you need X?/I thought you were doing perl" was what got me into sysadmin because I _hated_ dealing with other groups to deploy my code.