4 ms·
But what doesn't change? Network protocols? No, HTTP/3 is here. OS? Kernel, sure, but everything else no. E.g. most Linux OSs recently changed their entire in
by paulddraper 5y ago
But what doesn't change?
Network protocols? No, HTTP/3 is here.
OS? Kernel, sure, but everything else no. E.g. most Linux OSs recently changed their entire init system.
CPU architectures? ARM was irrelevant a few years ago. Faster CPU instructions are arriving every year. You say, "okay, well just recompile." Which brings us to....
Build tools? These are a nightmare to make stable in the best of circumstances.
It's all fiction. Code rot is real.
- hsn915 5y agohttp is not a networking protocol in the sense I meant. It's an application level protocol. Although you can still write a server that implements only http1.1 and it should still work fine. A lot of the things that you describe as changing don't really need to change. Operating Systems? Windows XP was probably the best windows, and it's from nearly 20 years ago. Looking at Windows 10, what exactly does it bring to the table? It's a much worse experience overall. Compilers don't need to change either.
- remram 5y agoHow often are changes in your web app directly warranted by a new init system or HTTP protocol? Does your code directly depend on what init system is running it, or somehow become unusable if it doesn't understand the latest HTTP version? If yes, just what the hell are you making?
- paulddraper 5y agoYes to the first question. My SystemD-based web server doesn't work in systemd. (Well the web server itself probably works, but the packaging needs to change.) As for the second, code can still work and yet be obsolete.
- paulddraper 5y agoTypo: "my system v web server..."