I highly doubt the law is settled on this topic and you’re assuming it is. I can’t see the courts accepting that your duplicate version of my work created through “magic” is not going to be a violation of my copyright. Especially if my work was included as input to the “magic box” that created the output.
Do what?
That doesn’t make it “no longer copy-written” though. The original copyright holder retains their copyright on it. I can’t see any court ruling otherwise.
There are reasons this hasn’t been done before.
There are a lot of things you’re not considering. You’d need to potentially re-partition a live mounted window disk(s) to create space for a Linux partition which could fail spectacularly. Or install over a running Windows system which will also fail very quickly.
Also - there are many tools that make it easy to create a live USB drive that one can boot from to get a taste of Linux in a way that is non-destructive and optionally install Linux.
I think I’d happily describe the multiple clipboard situation in Linux as a dumpster fire…
It’s awkwardly ‘solved’ by clipboard managers merging clipboards but it’s still wonky. Even for somebody who has been using Linux as a desktop for many years I occasionally find myself annoyed by it.
At this point I think I’d prefer “copy” to be an affirmative action rather than something that is done automatically. It makes pasting over existing text much easier.
You have the pi. Install Linux and find out? It takes like 10 mins… Otherwise it really depends on what you want to do and your expectations.
I’ve got a raspberry pi 1 (didn’t even have on-board wifi) that I just fired up the other day. It’s pretty slow but if you just wanted to do some simple python development it might be fine (depending on your patience for installing dependencies).
What do you mean “custom WM”?
There is no such thing.
Containers are just separated from the rest of your system by cgroups. You can even see the executable running in containers with ps and top. They’re native binaries running on the same kernel as the rest of your system.
Neat
Distrobox is not a feature of immutable distros. It runs just fine on Debian. As does flatpak.
Read again. You completely misunderstood.
Yeah, this is the “fun” of bazite. If you want to do the things it does well (desktopy things) it works well. But then things that are trivial in other distros are a pain. And the “solution” is to actually run one of those other distros in a container. It’s ridiculous.
Bazite is for people who want a computer to be like an iPhone near as I can tell.
Flatpak is simply a sandboxed application, similar to a Docker container. Its better to have natively installed applications over sandboxed if you are seeking the highest level of performance.
This is bullshit. Containers run natively on your system just like “native” [sic] applications.
I wouldn’t use arch for anything.
But even without , the arch way isn’t insane either: when something kernel-related breaks, boot with a live system on USB and fix it.
That is not a replacement for “arrow-key down during boot to select an older kernel”.
I have a server with a RAID card and the kernel at some point introduced a bug with the driver that prevented that server from booting. So I select the older kernel at boot, get the system up and running, mark that kernel as the default until the bug is fixed.
It’s not crazy, it doesn’t take long, you just need to know how the system works.
I know how the system works very well thankyouverymuch. But that’s an insane option when having multiple older kernels is so easy to do and common.
That’s… Insanity. Keeping at least one old kernel is amazingly useful if you run into issues with an update.
Don’t feel silly! It’s a common mistake, easy to fix, and easy to make. I’ve seen experienced developers do something similar.
It seems you’ve resolved the issue at this point but remember you can always run commands by specifying their full path as well (should you end up in a similar situation). All the PATH variable does is set the default locations to search when you don’t provide a full path to a binary.
e.g. /bin/ls or /usr/bin/vi
The wayland team simply doesn’t give a shit about that. They’re locked in an ivory tower debating the perfect protocol for allowing applications to position their own windows near 15 years after starting their project.