|
|
|
|
|
|
by aea65
2198 days ago
|
|
|
We have a title and don’t carry mops, my dear condescending developer who ostensibly doesn’t respect the entire ecosystem of people holding the Internet, the public cloud, and your entire CI/CD pipeline for whatever bullshit you’re cooking in NPM together. Do you have any idea how many “janitors,” most basically volunteer and most not employed by Amazon, are involved in the pedestrian aspect of merely making amazon.com land at the right place? Yes, this is a good future: who would ever want to touch the computers they operate? Better to rent computers and position the core competency of your business with a third party, right? Because you can shed some of those pesky janitorial salaries? I’ll be waiting by my phone when you’re on the verge of bankruptcy once the clouds have their teeth in your books, and suddenly I get promoted from “janitor” to “computer operator who has my interests in mind, even though I not-so-subtly malign his existence”. All you’ve done with this mindset is drive the same janitors to work for the clouds instead and contributed to the downfall of computing as a discipline that any player has any semblance of agency within, as the people who have actually touched datacenter equipment all work for them now or sit around in horror watching as a generation sympathetic to FLOSS arguments willingly hands over the reins of owning a computer to massive corporations. |
|
|
It's not that cloud is not the right answer. But people have started to forget that running your own metal is still an option. Or with current prices and performance: even a more viable option as it was in the past, because you can do so much more with so much less.
[1]: cranking out useless features nobody ask for while looking down on those (dev)ops people.