• 0 Posts
  • 101 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle
  • In that it’s not a kernel with just a c library and busybox

    This wouldn’t be a distro though, at least not in the context of the question being asked by the OP. My point being that Arch isn’t “minimalist”, because its not really any more minimal than Debian, or Fedora. It is more vanilla than them, preferring to not modify the original sources beyond their packaging, while Debian does do a lot more changes in this regard.

    Something like Tinycore, or Puppy are minimalist focusing on running in memory entirely, or Alpine is minimalist by focusing on reducing disk space. Debian, Fedora, or Arch installs, on the other hand, are basically the same in terms of size, unless you also consider them to be minimalist. At which point we are in agreement.








  • No amount of polishing that turd will make me ignore the fundamental user unfriendliness that is nested text drop-downs.

    Can you give me an example of this? From my perspective, using something like Kate, the extremely user friendly experience of discovery is vastly better than something like vi. In Kate, I appreciate the discoverability of having a list of options. I recently learned it can interact with LSP’s because of the menus. I don’t use it for that all that much, but it was cool to even know it could do that. Maybe vi is bad comparison, but off the top of my head GTK apps just have the hamburger menu, that then opens up the list of text menu options. Seems like its just hiding the option menus by nesting them in an additional layer of a button.

    For the record, I haven’t used a windows computer as anything more than an appliance in over a decade, so maybe the influence is lost on me.




  • Rebuild after every config change

    This is pretty much the whole point of using nix. The system is declarative, so it rebuilds the parts that changed, because all changes are imperitive and atomic. If it didn’t rebuild your sshd config and restart the service when you changed the accepted key types, what would even be the point? Coming from a huge ansible background nix feels like ansible on steroids.

    FHS incompatibility

    Why does this matter? Nix manages all your system binaries and PATHs just like any other distro, so why would it matter where they are kept? Programs like type/which still work exactly the same, and nix imports your dependencies exactly as described in the build scripts when you need to compile something locally.

    Its honestly refreshing to see a distro really pushing innovation like this by taking advantage of everything Unix systems are built with and doing something this cool.









  • I use NixOS, but before that I was on openSuse. I have not thought about Bluetooth in at all in the last few years. Zero issues. I pair it in KDE’s default bluetooth manager and then never really touched it since. Media keys all work, I control it over WiFi from my phone with kdeconnect no problem.

    I think a few months ago I had to turn my headphones off and on again when the quality got really low for a second. Reading this thread I guess I’m extremely lucky? I don’t produce music or anything like that, so I might not be taking advantage I’d some its more exotic features.

    EDIT: I am using a basic USB Bluetooth dongle I bought at least 8 years ago for my desktop, and my laptop just uses the built in Bluetooth. If that’s any consolation.