4 ms·
i think this is the key point of the article: it actually winds up being less DevOps work, on average, to support open-source systems running on bare VMs, than
by em-bee 6y ago
i think this is the key point of the article:
it actually winds up being less DevOps work, on average, to support open-source systems running on bare VMs, than to try to keep up with Google’s deprecation treadmill.
- disgruntledphd2 6y agoI honestly feel like this is a better idea in general, at least in data science stuff. For context, I tend to get dumped with undocumented poorly written untested DS code bases every time I move to a new job. The difference between setups where there's a bare VM/server and it runs using standard tools (command line scripts) or at least some open-source orchestration and any kind of proprietary technology tied to infrastructure is massive. Additionally, the server stuff can be maintained and debugged by a far larger number of people, thus reducing bus factor. Like, maybe in the web dev world there are things that everyone knows that are AWS services (maybe S3 counts, I guess) but in the DS world, I just know that I'm in for a whole lot more pain if they haven't just used bare servers.
- em-bee 6y agothis is the classic advantage of Free Software and Open Source over non-free tools. you often get a mix of commercial services and inhouse custom development that is no better documented or supported than FOSS alternatives.
- ithkuil 6y agoIs it true though? Keeping your stuff up and running, patched with the latest security updates takes time. And opensource systems also break compatibility at times. Sometimes the installation/upgrade process changes over time and you need to learn how to do proper upgrades even if the software technically can be made to work with the rest of the system. It's hard to quantify, but I don't think it's so clear-cut as Yegge makes it look.
- em-bee 6y agowell, being forced to adapt your system because a service provider is not allowing you to keep it running can be a significant drain on your resources. especially when you can't control when you do it. sure FOSS needs to be upgraded too, and sometimes there is change that you need to adapt to, but you are in control of the schedule, and if you are busy you can delay the upgrade work to when you have time for it. a service being shut down won't give you that flexibility
- ithkuil 6y agoThe timeframe is often quite different: Google gives you 12 months notice before turning off the lights. A FOSS tool "forces" you to upgrade when the old version you're using has a serious security issue that's is not backported. Which means that unless the supported version is fully backward compatible with your software, you have a quite tight schedule to deal with. Sure, you always have the "option" of running insecure systems. Unfortunately a lot of people choose that "option" and severely underestimate its cost...
- em-bee 6y agoyes but, an upgrade with some incompatible changes is still a world of difference compared to potentially being forced to rewrite a whole bunch of code because the system you used is completely discontinued and the alternative that replaces it isn't even remotely similar