3 ms·
I feel like all of the problems in the blogpost are solvable without moving everyone to this crazy web development environment. To quote one of the proponents:
by Boxxed 5y ago
I feel like all of the problems in the blogpost are solvable without moving everyone to this crazy web development environment. To quote one of the proponents:
> I do solemnly swear that never again will my CPU have to compile ruby from source.
...yeah, why was that even happening? Why not distribute pre-built artifacts? I feel like the whole docker ecosystem only exists because people forgot how to distribute software and/or python/ruby and friends make deployment so hard.
- rightbyte 5y agoFighting configuration complexity with another abstraction layer ... enabling the devs to pivot to pushing even more brittle code then ever before.
- mbreese 5y ago> Why not distribute pre-built artifacts? Back in the day (ahem), I’d have solved the problem by building new .deb or .rpm packages and letting the OS manage the updates for us. This is a lot harder for languages like node/js, ruby, python, etc… Dealing with a system level packages vs local packages is hard, so almost all management happens out-of-band. Older versions of packages was/is still an issue for many distro-managed libraries. And different projects have different requirements. In the end, I’m largely okay with this… I’d rather have my choice in local OS and be able to work on my client of choice. I see the rise of containers was more of a response to heavyweight VMs as a dev environment. But it’s good to remember — these are not unique problems and we’ve solved them all before.
- turminal 5y agoThey say in the post that everyone runs OS X, so incompatible local environments should not be a problem.
- deleted 5y ago[deleted]
- Terretta 5y agomumble mumble nix cough