5 ms·
You know, there once was a time when we did everything in folders and didn't need the overhead of containerization just to keep well behaved things from steppin
by AnIdiotOnTheNet 9y ago
You know, there once was a time when we did everything in folders and didn't need the overhead of containerization just to keep well behaved things from stepping all over each other and breaking everything.
Like all progress in computing we've reinvented the wheel, but now with a few additional layers of abstraction and the consequential performance degradation.
- Phrodo_00 9y ago> keep well behaved things from stepping all over each other and breaking everything Containers help with keeping bad behaviors from stepping all over each other.
- AnIdiotOnTheNet 9y agoYes, that's their value. You shouldn't need to use them for your development environment or normal every day software. Unless of course you're saying that most software in the GNU/Linux world is badly behaved, which I'd kind of agree with.
- sigjuice 9y agoContainers also decrease the likelihood of bad behaviors getting fixed.
- fauigerzigerk 9y ago>there once was a time when we did everything in folders Not on Unix though. "Stepping all over each other" sounds like the guiding design principle behind Unix's folder structure and dynamic library loading aproach. Docker's isolation is far more than just isolation of files and folders. It's more like J2EE for Linux :)
- saagarjha 9y ago> You know, there once was a time when we did everything in folders and didn't need the overhead of containerization just to keep well behaved things from stepping all over each other and breaking everything. Those were the days…when we didn't have stupid watchdogs like memory protection and preemptive scheduling, and we all shared resources nicely and fairly, all the time. There were never crashes because someone touched memory that they weren't supposed to, or hangs because someone decided they were more important than all the other processes. No siree.
- AnIdiotOnTheNet 9y agoWay to name some completely orthogonal problems that existed at the time. I'm surprised you didn't mention needing to go to a library to look things up or tie up the phone line to use the internet.
- saagarjha 9y ago> Way to name some completely orthogonal problems that existed at the time. What? These aren't completely orthogonal at all, they all fall under the umbrella of "process isolation" and containerization. There's a reason we have safeguards for processes in place; it's because it's a lot better when you have something to police badly behaved software than to trust that everything will work well 100% of the time.
- AnIdiotOnTheNet 9y agoYes, I can see why orthogonal was a bad choice of words here. Here's my point: those things mentioned were improvements on things that didn't work very well even for trusted applications that did nothing unreasonable. When your development environment or even regular desktop software spreads itself all over the filehierarchy as a matter of practice, conflicting and interfering with every other application because it does the same thing, that's taking something that used to work just fine and breaking it. Then you add a layer of abstraction like containers to solve the mess you created. Containers are a good idea for a lot of things, I just don't think I should need them to run normal everyday software.
- oblio 9y agoWhen was that time?!? Do you have a time machine so I can go there? That never happened... Maybe it happened in some tight academic environment for a few years, but once the cat was out of the academic environment, it basically never happened.