this post was submitted on 03 Apr 2024
96 points (93.6% liked)
Technology
58303 readers
15 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Dude, I learned how to write HTML in the 90's and even back then everyone knew that apache2 was clearly fucking superior. IIS has been a joke since the 90's when it was released.
I remember trying to get it to work with MySQL, failing, and moving to apache.
I had to do it for work at some point in the late 90s and IIS did actually had a pretty good configuration application whilst Apache was all text configuration files.
The problem was that IIS compared to Apache was heavier, less performant and scalable, not as stable and it required Windows (if I remember it correctly it was even heavilly tied to other MS software such as their database).
Apache did require a bit more expert knowledge to get going, but in all else it was already superior to IIS.
I'm surprised anybody still uses IIS.
Except that's not what was happening. IIS came after Apache and played a catch up for a while. It almost surpassed Apache in 2007, but GFC happened and its popularity dropped rapidly. If not for GFC, there would be no Apache today.
Nginx also increased in popularity around that time, giving more competition to IIS. Most of the web stacks I've seen recently are running Nginx.
(I'm an HAProxy man myself.)
NGINX is rarely used as a web server, it's usually used as a reverse proxy, cache and SSL terminator. Just like HAProxy, Varnish, etc.
How are we defining a web server? Because to me it's "the thing listening on Port 80 or 443 that responds to HTTP requests."
And, yes, I know they do more than that, but they also do those things quite a bit.
There's a pretty clear distinction between a web server and a reverse proxy if you work in the field.
I've got over 20 years of experience in the field. I've configured both of them as reverse proxies and web servers.
If Nginx is accepting connections on ports 80 and 443, terminating SSL, and responding to HTTP requests, that makes it a web server. Especially if it's responding with static content.
Oh my...