• 1 Post
  • 37 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle

  • I get it, I actually use the exact same distros you mention: Pop!_OS, Endeavour and Fedora.

    Had the same experience with Pop!_OS: those few things that did not “just work” but needed tinkering caused quite some issues. And yeah, somewhat more bleeding edge than Ubuntu LTS is nice: to use neovim on the 22.04 base, I’d need to use distrobox or build vim from source, but on Fedora and Arch, it “just works”.

    I liked Endeavour, though I haven’t really used it with a DE, I went with Sway. So hard to compare, but the manual sysadmin intervention everyone keeps talking about has been minimal. AUR is amazing, pacman is fast and sane.

    I went to Fedora because it is bleeding edge enough, but seems better tested and more stable than Arch. Also wanted to see how BTRFS is setup on there and test the rollbacks. The codec stuff has been terrible though. Even after enabling RPMFusion and installing a bunch of them, the Fedora source Firefox still refuses to do video calls in MS Teams. I’m using Flatpak browsers now but downloading flatpak updates is way slower than even the worst package manager for “native” binaries. Feels a bit odd to have to use a Flatpak for the browser.

    If I had to install a new pc today, I’d go EndeavourOS with KDE (which I’m using on Fedora now), BTRFS and systemd-boot. I got to know systemd-boot in Pop!_OS and have tried a different boot manager (rEFInd), but systemd-boot is amazing.










  • This is excellent! Each step can be Googled but for a quick summary:

    A wine or proton prefix is like a small Windows filesystem inside your Linux. This is how you run most games. Steam normally hides this from you, but it does this exact thing: one proton prefix per game.

    On Nobara and Fedora, you will not need to worry about duplicating files and wasting space at all: they use a very advanced filesystem which (among other things) does not actually repeat files but just goes “this file is the same as the earlier one, just read that” and saves on disk space that way. You don’t see this in the file explorer, you can just copy a file a hundred times but it will not consume a hundred times the disk space. Very cool stuff. And very useful with proton tricks.



  • Fair point, but the engine is important.

    I understand their blog post, and if I were to build a browser today, I’d probably do the same.

    But that doesn’t mean this situation isn’t problematic. It’s similar to car-centric infrastructure: in this situation, for any individual, choice X makes sense, but that will make the situation even worse for the whole population. A cumulation of many tiny Prisoner’s Dilemmas.




  • Good points all! I think OP, like me, is not afraid of manually messing with config, reading archwiki and getting your hands dirty.

    But I would’ve never looked at dracut when setting up Arch. I’m really happy Endeavour set that up for me. It’s nice to have a good base. Btw, thus dracut also meant I didn’t have to do anything with the mkinitcpio change you are linking. Although I was reading the wiki, forum, and looking forward to it.



  • F04118F@feddit.nltoLinux@lemmy.mlHelp deciding Os
    link
    fedilink
    arrow-up
    5
    ·
    4 months ago

    As a Python dev, I think I may understand your desire to get away from Windows. I have often encountered Python tools and frameworks that don’t work on Windows but do on Unix (Linux and MacOS), like Flask, but can’t recall seeing the other way around.

    If:

    • Your laptop is still receiving security updates from Apple and is performing well,
    • And your main focus now is to learn Python

    I would not mess with it and just stick with MacOS.

    If your laptop is no longer supported or it is getting too slow, or if you want to play around with Linux, that would be a good reason to move away from MacOS.


  • I agree that Konsole are Kitty are both lovely terminals that are very configurable. Kitty for text file people vim enthusiasts and Konsole for GUI lovers.

    By “questionable update policy”, do you mean that it is updated by the package manager when installed from official repositories but it has an auto-updater functionality for users installing it manually?

    IIRC someone who compiled from source but didn’t set the flag/config to disable the auto-updater was surprised about that.

    I don’t see the big deal of it to be honest. The vast majority of users will be installing through the package manager. If you compile from source, you can decide yourself whether you want it to auto-update. The whole point of compiling from source is the extra control, not the defaults, I’d guess. Unless you don’t know what you are doing and the package was not available for your distro and in that case, enabling auto-update by default even serves that user group.