> better understand how your software is hosted in the cloud on Linux servers
Since the days of Apache/PHP I don't think people (need to) host their dev work on proper servers at their local computers. So this argument is kind of invalid unless you want to set-up your dev machine as some kind of dummy server.
> Since the days of Apache/PHP I don't think people (need to) host their dev work on proper servers at their local computers. So this argument is kind of invalid unless you want to set-up your dev machine as some kind of dummy server.
True, and false
I do host the cloud software I work on on a local machine (running Debian-12) because it is easy. I do not need to, I want to and it makes me more productive
I also spend a lot of time in a terminal on a remote machine. I have to be careful to not get the two confused (I use different background colours for terminals on different machines.)
I have done the "remote terminal on cloud software" on Windows - a difficult and painful experience. Tools I take for granted, and get gratis, on Linux are not there on the Windows servers.
What ever flaws the article has it is not out of date
This has been my observation, I think people will get caught up in the details but most dev workflows I see now are either containerised (docker etc) or serve themselves (rails, node, even PHP can serve itself with no webserver)
I see less developers setting up local servers and managing them for development purposes. Containers are not the same thing, for the purposes of this commentary on how people work now.
Since the days of Apache/PHP I don't think people (need to) host their dev work on proper servers at their local computers. So this argument is kind of invalid unless you want to set-up your dev machine as some kind of dummy server.