

The Wayland security model is far more restrictive. Accessibility tools need to screen capture, create input events on your behalf, etc. Such things aren’t possible under Wayland (yet?).
The Wayland security model is far more restrictive. Accessibility tools need to screen capture, create input events on your behalf, etc. Such things aren’t possible under Wayland (yet?).
It’s not my fault they make running apps from the cli so irritating. Broken by design. Even snaps work better.
So, containers do not get you reproducibility.
You absolutely do. If you build a container and publish it you will pull down that exact thing every time. How is that not “reproducibility”?
You no what though? Scratch that - who gives a fuck? Bit-for-bit reproducibility takes far more effort than it’s worth anyway. Even NixOS isn’t completely reproducible. It’s a false goal.
For dev environments, repeatable is okay.
It’s well more than good enough you mean.
If you want actually reproducible binaries that you can ship, Nix is better fit for that purpose.
Nobody really needs that.
docker build . -t docker.company.com/build-env:1.0 && docker push docker.company.com/build-env:1.0
But for like 99% of development teams “repeatable” is Good Enough™.
Containers also don’t give you reproducible environments, and Nix does.
Of course it does. 🙄
sigh, yes it is.
Meh. So is docker.
You couldn’t figure out how they make money? This took me like 1 minute to find.
This is the way. Ansible is underrated by the self hosting community.
ctrl+a and ctrl+e are from Emacs.
I once ran ‘chown -R root:root /’ in a misguided attempt to solve some permissions issues I was having. 0/10, do not recommend. It turns out a lot of system things aren’t root owned…
Running a stupid command and learning from it is part of the learning process.
It’s not uncommon to have your Dockerfile curl https://host/file.tar.gz
and then tar xvf file.tar.gz
into the filesystem somewhere.
You don’t want to use snaps in docker containers. They need systemd and stuff that are going to be a real pain to get working.
“I use Nix, btw”
You say “The Windows Memory Subsystem” not “The Windows Subsystem for Memory”.
Windows Linux Subsystem would likely be most clear.
It’s very annoying that the community hasn’t standardized on an approach for proxy settings.
OP stated that a VM is not feasable because of ressources on the PC.
I very much doubt that is true. Most standard issue system these days should be able to run an emulator well enough to run iTunes.
🤷♂️
Wut?
This! KDE’s settings are a mess to navigate. I completely understand why that person didn’t know there even was a configuration for this.