• 0 Posts
  • 8 Comments
Joined 1 year ago
cake
Cake day: October 2nd, 2025

help-circle

  • It doesn’t matter what the reason for its creation is, you can make similar arguments about laws against assault and murder or the right to vote, what matters is what it’s doing in the current legal situation.

    If you think that the end of copyright will suddenly render corporations powerless, you are beyond naive. Some will fail to adapt, undoubtedly, but many will not just adapt, they’ll be able to take full advantage of this new situation. Copyright isn’t the only mechanism they can dig a moat with, and as long as the economic incentives remain what they are, they will find a way and be no less exploitative. Meanwhile, the individual creator or indeed projects like Linux will lose what little protections they have and be completely at the mercy of these monsters. Forget exploitative contracts, they can just exploit you without one!

    A better world without copyright is possible, it just doesn’t look exactly like this world, except without copyright. The abolishment of copyright is not an ideal, it’s a means to an end. But for those means to lead to a good end, how and when it happens matters. To cheer on a development because it nominally achieves what you believe is needed to lead to your ideal outcome, even when the way it happens would lead to an outcome that is in direct opposition of the ideals that lead to that belief in the first place, is a sign you’ve stopped thinking.



  • The thing is, if all other things remain the same, an absence of copyright will also be used by the wealthy and powerful to further enrich and empower themselves and as a tool of oppression.

    From the Ferengi Rules of Acquisition:

    #34 War is good for business.

    #35 Peace is good for business.

    You cannot have internally consistent, principled view on copyright without also having a compatible view on the economy. And even then, the economy needs to come first; you cannot start destroying load-bearing pillars, no matter how ugly, without first getting everyone out of the house.

    The tool in itself can really be usefull when well used. Many people use it and get nice results.

    The way I see it, there are two kinds of people: those to whom AI is utterly useless because it just ends up taking more time and have them burn through their cognitive endurance faster, and those to whom it would be irresponsible to let them use it, because it would prevent them from finding better solutions for the busywork they’re letting the AI do, and they just end up creating a lot of needless maintenance overhead.

    But more importantly, being “useful” to certain individuals is not the same as being good for society. Which brings us back to it undermining licenses like the GPL, which would further enrich and empower the already advantaged.

    Also, I can’t find any example in history of a technology that was successfully banned despite being usefull.

    CFCs? Asbestos? The bans on them aren’t perfectly enforced, but nevertheless, the hole in the ozone layer is shrinking and the number of people dying of asbestos-related lung cancer is reducing, so they do have value.

    The strict “no-AI” movement has already lost its battle

    Even if it were true, that would be no reason to stop trying or to stop saying the truth: No matter useful you experience it as being, you are causing harm. To yourself, to the field, to society.



  • Analogies are comparisons of structure, not intensity. There are a lot of things that are “not as bad” as child labour, that doesn’t make them OK.

    But i don’t believe in copyright laws either. Do you believe in the goals of the GPL? Because you have to admit, the way AI works, regardless of whether you frame it as “theft” or “copyright infringement” or not, is at odds with those goals.


  • GPL may call itself “copyleft”, but legally it is dependent on copyright to be enforceable. In the first place, the whole point of licenses like GPL is to ensure that when people take from the commons, they also give back to the commons. The way AI gains its ability to generate shitty code undermines this, and so is ideologically very much at odds with Linux and the wider FOSS world.


  • Omarchy is basically where someone takes Arch Linux and says “I want it to have this window manager, this terminal emulator, these programs installed by default and to have this configuration” and shares it with other people. Since Arch by itself is pretty bare-bones, this sort of thing can be useful for people who want to use Arch but don’t want to spend the time making a functional system. Since you’re using NixOS, I’m sure you’ve seen other people’s .nix files being shared. This is similar to that, but more formal and because Arch doesn’t make it as easy as Nix, it’s shared as its own distribution instead.

    Because the goal of Omarchy is just to make something bare-bones into something immediately usable, it’s more meaningful to compare NixOS to Arch Linux directly. The most fundamental difference between the two is the package manager, so the way software installations are managed. All package managers have to (usually) download a package and, if needed, its dependencies, extract it to somewhere on the file system where it can find it, run an initial setup script, make it so that you can run the executable by name instead of needing the whole path, and do some bookkeeping so that it knows what is installed, and so, what needs to be kept up to date, what can be removed etc. But there are different approaches you can take to achieve this.

    Nix, as I’m sure you’re aware, is a declarative system where you write a program (even if it doesn’t always look like one) in a functional language, and when you update the system it runs that program, which outputs what is basically a list of packages (among other things) and then it compares that list to the installed packages and installs/uninstalls/updates packages so that it matches the list.

    On the other hand, Pacman, the Arch Linux package manager, is a more traditional imperative system, where you explicitly tell it to install/uninstall/update packages.

    There are other differences, like how Nix can have multiple versions of the same package installed, but Pacman only supports one, and there are differences in philosophy between package repositories on when packages should be updated, whether to allow proprietary software etc.