The backbone of the internet.
It’s still not working , and it’s been two days.
Software is cobbled together with ducktape and cowchips.
After 10 years in the field. My take is:
We’ve lied to ourselves so much that we believe our own lies
The backbone of the internet.
It’s still not working , and it’s been two days.
Software is cobbled together with ducktape and cowchips.
After 10 years in the field. My take is:
We’ve lied to ourselves so much that we believe our own lies
In all cases, this has nothing to do with t to he question. It wasn’t about how smart you have to be to set it up yourself, it was about how robust or fragile it is once put into place. A better point would be that we had certificates with ten-year expiration (not fragile) but susceptible to a myriad of advanced security issues. The solution was to reduce that to certificates that expire every few months, held together by daemons and scripts that renew them automatically in the background, significantly increasing the number of simultaneously moving parts and making the whole more fragile (with obvious security benefits).
More complex = more smartsss.
I want to move away from model T, I want a F150 with push to start
There are plenty of later model cars that add back seemingly unneeded complexity for little gain that would be better examples.
To add to your point: I chose the most popular stack with the biggest mindshare, just in case something goes wrong, I’m a one man shop, but why fight against it.
I’ll try Ngnix…
It really only exists because it was the only option at some point in the past and software grew up around it so it kept momentum.
If you're doing anything new you wouldn't use it at all, and instead use one of the multitude of servers that are far simpler and better at the same tasks.
example.com { reverse_proxy localhost:9000 }