AFAIK everything was dropped in the end, and people went back to using audacity

Yeah, who’d hate using a package manager that increasingly slows down your boot time with every package installed, or that uses a closed source store to provide you FOSS

Maybe there’s a reason canonical has to force it on their users

No, Debian doesn’t take your apt install ... command and install a snap behind your back…

I dislike that it takes way too long to boot

1. Use the Daemon, it starts a new client in a fraction of a second
2. Improve your config and it’ll start in under a second anyways

Emacs had some “premade IDE” project I recall that I tried and wasn’t that enthusiastic about.

Doom Emacs, spacemacs, etc.

And there are plenty of nvim “distros” like that (lazyvim for example).

They make getting started pretty easy. I’ve been using Doom for years and never bothered to make a full config of my own.

AI is quite fit for the task of understanding

Sure, and parrots are amazing at spotting fallacies like cherry picking…

Icy peepee

Or

I see peepeee

???

73 and 76, but I got them mixed up, ed is older.

That’s for original Emacs though, the gnu version came out in 85

Emacs is older than ed

Separate your system and user lists. Use home-manager for example for your user packages. I think separating those configs is the official recommendation.

As for the rest, I’m using nix on MX because of declarative package management. Screw going back to imperative and having to remember what packages to install. If it’s something I use often it goes on a list, if I don’t nix shell comes to the rescue.

I’d rather mess around with dev envs for nix than distrobox.

Damn you broke my brain for a second there. I thought you meant that nixos replaced k8s, and was wondering what the hell are you talking about.

Hell no, Emacs and nvim UX is far superior. I won’t ever go back to clicking.

I was talking about regular fedora. It’s not that you have to reboot, but you don’t get to use those updates until you do. The most obvious example is updating the kernel and its modules.

Linux almost never needs to reboot after an update

Doesn’t it often need a reboot to apply some updates?

I rember reading something along those lines then I was researching why Fedora installs some updates after a reboot. Most

https://rosettacode.org/

And I think they rewrote a bunch of C libraries in order to have a better cross-platform compiler for C and zig. Or something along those lines

You can’t replace it.

Zig?

https://www.gnu.org/licenses/license-list.en.html

GPL is hard or tough to monetize

What do you mean?

stuff will get even spicier when we have conservations whether code is asset itself (especially scripts).

That’s true. What about LGPL?

e.g. don’t touch AGPL code unless you also use AGPL

Just to clear this up: copyleft licenses, GPL variants for example, require the license of your code to equally preserve the freedoms provided to your users, or in other words also be a copyleft license. There are some loopholes like GPL on a server, but be very careful when using copyleft code unless you want to use a copyleft license as well.

It gets somewhat murkier when you use someone’s code and base yours on that. IANAL, and that’s very much the legal territory. If at all possible, just reuse the original copyright and license and then derive your work (given the license allows that).

That all depends on the license AFAIK, but IANAL. Most FOSS licenses allow you to do whatever you want while preserving copyright claims, and that includes rewriting or changing the license. GPL forces copyleft, so even if you rewrote it from scratch, you could still be liable if you saw the original code.

For example I’ve heard that corpos bootleg copyleft code by having completely separate teams doing design and implementation. The implementation team can’t ever see any part of the original code, and they have limited communication with the design team. I think that would also go around the copyright claims as well.

If at all possible, just reuse the original copyright and license and then derive your work (given the license allows that).

Or just slap a GPL and subsume everything within a vortex of FREEDOM, and thusly become a true FOSS dude