drndramrndra

joined 8 months ago
[–] [email protected] 1 points 7 months ago (1 children)

Here's a prediction: not even fedora will drop it by 2027.

Wayland still doesn't work for a lot of people, and the ecosystem is nowhere near mature enough. I doubt enterprise distros will consider dropping xorg until their users can actually work on Wayland.

[–] [email protected] 2 points 7 months ago (1 children)

IMO too much "Tutorial", not enough Review. For example:

The spectrwm workflow is unique. It took me awhile to become acquainted with the standard flow and gain comfort in using it. I did have to bend, fold, and spindle the environment a bit

You haven't written a single word on how it's different from any tiling manager, nor what and why you changed.

Generally the article feels like the first comment in unixporn, where you list out your relevant dotfiles. The only extra information is that you like it, and a list of dependencies for your config.

[–] [email protected] 1 points 7 months ago (3 children)

Oh no, a wm might die in a few decades! Anyways...

[–] [email protected] 4 points 7 months ago

Tumbleweed is recommended often here.

I occasionally try out Opensuse since like 2007, but I always find the alternatives better. Why Tumbleweed over Arch, why Leap over Fedora/Debian, why suse over RHEL?

[–] [email protected] 2 points 7 months ago* (last edited 7 months ago) (1 children)

Is any popular stable distro free from corporate influence aside from Debian?

[–] [email protected] 1 points 7 months ago

This shows something else. The traditional languages are all more common than Rust.

It's a survey from 2019, but in those rust is traditionally the favourite language nobody uses professionally.

I suppose Go could be a good competitor, and I read a thread comparing C=Go, C++=Rust.

Go's syintax is C inspired, but it's not made to replace it, nor do they compete in the same space.

Look at zig instead of you're interested in that.

I am interested in a discussion about that, as I would like to learn one of these languages

Skip rust unless you have years to get good at it.

[–] [email protected] 3 points 7 months ago

TIL GPL is a proprietary licence

[–] [email protected] 6 points 7 months ago

You never saw an IRC chatroom archive?

[–] [email protected] 0 points 7 months ago

If you're running unstable system packages, immutability won't really save your stability.

So don't complicate it, and just use Debian with nix and home-manager. That way you have a stable base, and you can create a list of bleeding edge packages that should be installed. In any case it should be essentially only docker + whatever can't be dockerised.

[–] [email protected] 2 points 7 months ago (1 children)

I feel that they're not close to the ideal system I have in my mind.

Check out something stable + nix. Just home-manager with a list of files to install, keep it simple. I'm currently running it with MX. I'd prefer guix, but nix is a lot better package wise. Guixos gave me too many headaches, for not enough benefits.

To truly appreciate lisp parens, use something like lispy or paredit. The uniformity of the language allows for some really cool editor utilities.

[–] [email protected] 1 points 7 months ago

Debian + nix unstable and you get the best of both worlds. Bleeding edge userland, and the system always boots^btw

[–] [email protected] 3 points 7 months ago

AFAIK no distro forces you to reboot, but they all require it for some updates to take effect. You can't reload the kernel while the system is running.

Fedora just makes that clearer to the user by only installing those updates when they're going to be active - after a reboot. I think it also blocks new system updates until the current set is completely finished.

You can disable offline updates in the system settings, but I think they're a good idea, especially for the average user.

4
submitted 7 months ago* (last edited 7 months ago) by [email protected] to c/[email protected]
 

Idea: Debian + Nix == stable and funky fresh

I first came across Declarative Package Management in the manual. So I started making these packages based on it.

The install works (nix-env -iA nixpkgs.my-emacs), but nix-env -u doesn't update changes (adding and removing packages from the paths). Do I need to reinstall my- packages to get updates as well? Does nix-env -u update package definitions (apt update)?

After that I came across zero-to-nix. This approach wasn't mentioned at all in the quick start, and I came across comments that people shouldn't use nix-env anymore. Should I create flakes instead of packages, and export their paths to have them available globally?

How do you use Nix to manage your packages? Do you have any examples?

nix-env/nix profile/home-manager?

view more: next ›