F04118F

Exactly! If you only have to edit small text files on a server once in a blue moon, nano is much less biomemory-heavy. But if you regularly write docs and code in l vim or neovim, it starts to pay off after a week or two.

I really enjoyed learning to quickly select and change entire words or lines, doing things like: :%s/replace_this_text/with_that/g Etc. If you enjoy that, you will soon get to a point where you miss the motions in your regular editor and install a vim extension in VS Code and stuff, just before fully switching to neovim

Try running this: vimtutor

If you are already aware of hjkl, skip to the part where you learn motions:

/motion

Then look up surround (ysw is usually the command to surround a word, ys3w the next 3 words, etc)

It's pretty neat.

That's amazing!

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.

Genuine question: what is it about Fedora that keeps you coming back? I have also used Debian based and Arch based distros, as well as Fedora.

Ubuntu does not require the model either. It's an optional service that Canonical offers. They just market it in a weird way (inside the package manager)

I've been trying to explain that choosing to pay for this "extended security service" this is completely unnecessary if you just upgrade your OS every few years.

I think the average Mint user is not a wealthy enterprise with tons of systems they don't want to upgrade so they don't need to consider this, whether it's available for their distro or not.

IIRC, Canonical is using Ubuntu to push an "extended security maintenance" program or something like that.

These kinds of services are all the same. RedHat does it, Microsoft does it, many others too probably.

The idea is: (stop reading if any of these don't apply)

• You are a huge enterprise with lots of money
• You have a lot of computers with a lot of complex, (manually tested and badly designed) programs/systems that are strongly coupled to and dependent on the specific configuration of those computers.
• Thus, you HATE upgrading all these computers to new OS versions
• You would love to pay a company to give you a sense of security by providing monthly security patches so you can keep using your old OS
• You don't really mind that this is fundamentally flawed and insecure because the cost of upgrading to a new OS version is too great for you to pay: you'd rather take a subscription for shitty bandaid.

IIUC, yes

Wayland Nvidia compatibility will be here soon™ Nvidia drivers needed explicit sync, which was not supported in Wayland. However, explicit sync has been merged into the Wayland protocol and should be here shortly. Gnome 46.1 already ships with it.

I do not understand fully but maybe drivers need a bit of configuration too to use this? I'm not sure of all the steps but it should be here soon

Could be a (too) old version if you're still on the Ubuntu 22.04 base