One I follow is the KDE Blog (https://blogs.kde.org/index.xml#feed)

Yeah, I started my journey in about 2001. Linux was definitely more geeky back then.

I’ve used it on Endeavour for about a year and on Tumbleweed for eight years before that with no real problems other than plasma-shell occasionally restarting. I have Nvidia and the open drivers.

So I suppose you never use a browser to run a web application on the desktop :thinking_face: Anyway it;s a client server architecture designed for remote installation on servers as well as local installations. It makes sense to have one installer do both.

As to the old installer, when you knew about the un-obvious features, it was brilliant from a user perspective, but I’m willing to bet that from a developer perspective, it was hard to maintain, hard to add new features to, and fragile.

That’s kind of like asking why we’re not all driving Ford Model T cars, after all you could drive in them just fine. Technology moves on, best practice moves on, Hell, everything moves on.

A quick glance at the Agama repository suggests that the server is written in rust and the front end in react. I’ve no idea how it all works in practice as I don’t use Tumbleweed any more. I really liked the yast installer but it was getting old.

Why isn’t everyone working on Arch instead of wasting time with all those other distros?

How often do you look at your keyboard anyway?

More than I care to admit!

Just to add, I have been told by people who know, that you should always update when installing a new package because not doing so can leave your system in an inconsistent state. Just get into the habit of running pacman -Syu <package-name> or if you use yay, yay -Syu <package-name>

The difference is that most of your software is built for your distribution, the only exception being some proprietary shit that says it supports Linux, but in reality only supports Ubuntu. That’s my pet peeve just so that you know!

Ctrl+D sends EOF, so no it’s not like enter.

You’ll never get perfect binary compatibility because different distros use different versions of libraries. Consider Debian and Arch which are at the opposite ends of the scale.

The biggest problem with wsl is that you have to have windows as well.

If you’re developing specifically for Windows, you’re going to need Windows somewhere in the process be it bare metal or vm. You will also have problems with Excel on Linux although you could try the online one.

Jeffrey Combs was also in B5

Oh yeah, so he was.

Wayne Alexander, he’s the Jeffrey Combs of Babylon 5

As a complete newbie with those specs, I’d try Mint Xfce edition.

Flatpak kcm is the permissions control panel. link. With the n switch, you may have removed the dependencies, some of which look vital to me.

I’d managed to forget all about ndiswrapper until this very moment!

She was also quite embarrassed. As a fix, we moved her keyboard a few inches.