KindaABigDyl

joined 1 year ago
[–] KindaABigDyl 5 points 1 year ago

Already on 6.4.1 lets go

[–] KindaABigDyl 1 points 1 year ago (1 children)

Idk about "new Gentoo," as they're going for different things, for sure, but a lot of the reasons people like Gentoo seem to be true for Nix. Definitely still give Gentoo a try some day.

I used it for a few months and only moved on bc compiling was taking too long and was annoying me :)

[–] KindaABigDyl 2 points 1 year ago (3 children)

The way it feels is like getting the benefits of a source-based distro like Gentoo without the tradeoffs of things like compile times.

[–] KindaABigDyl 5 points 1 year ago* (last edited 1 year ago)

You have outdated information. There are no longer any tradeoffs to AppImages:

  1. Yes there is no "official" default installation path, but like how XDG_DATA_PATH isn't technically a standard but practically it is, the de-facto standard is ~/Applications now, and most AppImage-based tools respect that.
  2. They integrate fine with the system. Better than Flatpack and Snap, actually. I've had lots of issues with flatpaks not respecting themes, but never AppImages. Not sure where you got that from.
  3. I solved the other problem with AppImages with a package manager I wrote. Centralized location pointing to AppImage urls, and it downloads and keeps them updated. And no, you don't need to write your own, there are multiple AppImage package managers out there.

On the flip side, there's no weird extra locations like how flatpak installs apps, you know exactly where the program is in case you want to launch it manually, you can mix apps available in your package manager with ones you download directly seamlessly, no dependency hell or version problems as AppImages are self contained (even multiple versions at the same time), etc, etc, etc all the benefits people spout about AppImages.

AppImages imo are the superior cross-platform package format as there are no tradeoffs and no downsides, meanwhile:

  • Snaps are slow and proprietary
  • Flatpaks suck to create and maintainers select-all on sanboxing, defeating the purpose, so it's a complicated mess for no reason, and they also have bad theming that never works half the time.
[–] KindaABigDyl 4 points 1 year ago* (last edited 1 year ago) (7 children)

I prefered AppImages, but now that I'm on Nix, I've gone back to native. Native packages work well in the NixOS ecosystem.

[–] KindaABigDyl 0 points 1 year ago
[–] KindaABigDyl 0 points 1 year ago

NixOS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

[–] KindaABigDyl 34 points 1 year ago (14 children)

Lol is it really free of Western technologies if it's running on Linux?

[–] KindaABigDyl 1 points 1 year ago* (last edited 1 year ago)

Sorry I didn't know there was a difference. I thought Doom Emacs was a version of Emacs, not something that worked alongside the original. Like I said I'm a neovim user

[–] KindaABigDyl 3 points 1 year ago

Oops lol

Leaving in

[–] KindaABigDyl 4 points 1 year ago* (last edited 1 year ago) (3 children)

Arch does not have a place though. It's just a more buggy Arch with a worse maintaining team

EDIT: Actually, tbh it's incorrect to even call Manjaro Arch. That's an insult to Arch

[–] KindaABigDyl 6 points 1 year ago* (last edited 1 year ago) (2 children)

Not an emacs user, but probably there's an option for emacs that will allow you to embed your emacs config into your nix config.

If you'd rather have a separate file, you can install files to /etc/ via the environment.etc."<file-name>".source = ./file/in/your/nix/repo or using home-manager with home."<file-name>".source = ./file/in/your/nix/repo

I'm a "put it in the nix config" guy myself, and that's how I set up neovim

view more: ‹ prev next ›