I've recently spent a fair amount of time trying to peel my blog away from my existing framework due to how much I hated using docker to just build a website, it doesn't need to be this heavyweight.
That's one of my dilemmas. Due to using BSD and relying on jails I have a hard time using lots of possibly nice apps being released nowadays because they only offer the docker way of installing.
Virtualization was supposed to reduce the overhead, not create entire DevOps departments.
Years of containerization yet no real use over make clean; make build
Wanted to deploy your app in the "cloud" anyways for a laugh? We had a tool for it, it's called rsync
Let's run a virtual container in --privileged mode, so we can manage system resources from it -- Statements dreamt up by utterly Deranged
Look at what tech interviews have been demanding your Respect for all these years.
(These are real documentation examples for how a simple virtualization supposedly works)
I don't like containerisation because it leads to bullshit like atomic distros. I don't want a spicy Android.
Steam OS has some cool elements like the menu, the in-game side panels and the game mode/desktop dichotomy, but incremental rolling release is utterly deranged from my POV as an Arch user (btw).
Say Plasma "breaks" - a wiki will not help fast enough.
I'm not trying to defend rolling release for a gaming console, but give me at least the option to decide for myself whether I'm ok with breakage or not. There is this kernelspace NT driver that I wanted to try, but I couldn't because pacman is locked.
I'm currently trying Fedora Kinoite and from the get go the hassle of getting a proper Firefox+codecs to watch online videos feels like a major step back.
Then you have the issue of installing software in flatpack (is: vscode, texmaker) that are either not fully working of need to have their access tweaked. Atomic distros appeal is to "just work" it doesn't seem like it does.
For real though, containerization isn't the only way to separate applications from each other but totally fine, it's the "It works on my machine, so here's my machine" mentality that doesn't fill me with confidence. I've seen too much barely-working jank in containers that probably only get updated when a new version of the containerized application itself is released.
Nix can build you a bit-to-bit exact environment for your app. It is a superior environment, but is hard to use in the beginning and users can feel snobby sometimes. It is awesome, but YMMV.
I like containers. But they do have a habit of nurturing cludgy temporary hacks into permanent infrastructure, by sweeping all the ugly bits under the big whale-shaped rug.
I both love and hate this so much. The performance and recording is incredible but any super tech nerdy parody just causes me immense internal cringe. I couldn't make it more than a third of the way through that and I love working with K8S.
I would vote for docker as well. The last time I had to inherit a system that ran on virtual machines, it was quite a pain to figure out how the software was installed, what was where in the file system, and where all the configuration was coming from. Replicating that setup took months of preparation.
By contrast, with Docker, all your setup is documented. The commands that were used to install our software into the virtual machines and were long gone are present right there in the Docker file. And building the code? An even bigger win for Docker. In the VM project, the build environment for the C++ portion of our codebase was configured by about a dozen environment variables, none of which were documented. If it were built in Docker, all the necessary environment variables would have been right there in the build environment. Not to mention the build commands themselves would be there too, whereas with VMs, we would often have developers build locally and then copy it into the VM, which was terrible for reproducibility and onboarding new developers.
That said, this all comes down to execution - a well-managed VM system can easily be much better than a poorly managed Docker system. But in general, I feel that Docker tends to be easier to work with than a VM. While Docker is far from flawless, there are a lot more things that can make life harder with VMs, at least from my experience.
Programmer Humor
Hot
This magazine is not receiving updates (last activity 0 day(s) ago).