Most KDE apps will run on Gnome and vice-versa, but they might not run particularly well under those conditions.

I used to run into issues with this all the time. Recently, I find, for poplar apps, there’s always a version built for my chosen desktop environment.

Of course, I’m not very picky, anymore: Libre-this, Open-that, Free-Whatever. I usually find the one that comes up in the app search is good enough for what I’m doing.

I feel like linux demands an understanding of the relationship between hardware and software more than windows does.

Yes, when we install Linux on something that didn’t ship with Linux installed.

But in an apples to apples scenario - pre-installed OS provided by the manufacturer, it’s Windows that comes with more bullshit.

And there are (finally!) plenty of options to buy a pre-installed Linux computer, today.

It’s a tiny fraction as many as pre-installed Windows or Mac, of course. But it’s still plenty. There’s a half dozen companies with solid reputations and hardware specialties, and I only need one.

I haven’t especially heard the Linux or Rust stereotype, but it’s fair enough for a funny joke.

Stallman is one of the world’s most prolific C developers, so that part of the joke may be just making fun of his (likely) reluctance to adopt Rust, which is often recommended to C programmers.

I had not heard of Trinity Desktop. That does look like a much simpler path to beautiful Windows XP stylings.

Apparently, many people want to make Linux look like Windows 95?

I’d say Linux is somewhere around early Windows XP when it comes to usability for a normal person.

I was confused until it struck me that maybe you don’t consider Windows XP the peak of operating system user interface design.

I’ll admit, Vista really messed with my perspective.

That’s why we got together and agreed on one version of Linux to recommend to new adopters.

Even technical folks aren’t huge fans of RTFM.

If I’m doing something incredibly interesting, and I’m asking for help, I should RTFM.

If I’m doing something routine, we can (and usually do, now), make it simple enough not to need a manual.

Oof. Sorry you had such a bad experience.

Pro tip for others: It takes time for volunteers to reverse engineer new proprietary laptop hardware.

If the laptop manufacturers aren’t advertising Linux support, it’s up to the community to play guess and check, to figure out what the proprietary drivers do.

You might get lucky and pick the same exact model as a passionate reverse engineer. Or you might not.

With old stuff, your odds are much better that someone has figured it out for you.

For new hardware, it’s still essential to pick a vendor that chooses to write and release Linux drivers.

This will get better when truly open hardware platforms gain popularity.

I’ve never had any issues with any VSCode plugin failing in VSCodium.

But I’m not a PyLance user.

That you can have multiple terminal panes open to accomplish a small portion of the above?

Yes. Obviously. Two conclusions available to you are, either CLI developers are idiots, or they have tools you are unaware of.

The answer to “how can anyone work this way?” is out there, if you’re really interested.

People insisting on using the command line for everything is like a carpenter that only buys a circular saw and refuse to buy any other saws. Like yeah, you can do almost any cut with a circular saw, and it’s not a bad place to start, but theres a reason carpenters don’t limit themselves to a single type of tool.

You’ve just given the usual argument for learning Vim.

Having mastered both, my lack of patience for GUI tools is just that: impatience. I can use any tool, but I reach first for the fastest.

Everything you can do in VIM, you can do in VSCode running VIM in a terminal, but not the other way around.

You would sure think so, right?

But the VSCode plugin ecosystem still lacks some features available in the Vim ecosystem, and (fl just for example) LazyVim has most of the features available in VSCode.

At the end of the day, the biggest difference is speed. Even very brief unexpected delays can break my concentration. While VSCode is no slacker, it still has some delays, probably mainly because it’s still JavaScript under the hood.

Once there’s a GoLang, Rust or C port of VSCode, I may well switch permanently.

Is there a stable way to use closed (edit: intentionally DRM-ed) extensions (like the MS Python one) with vscodium by now?

Yes. Use this config edit.. Everything (edit: not written by assholes) works fine.

Edit: Damn. PyLance’s developers are up to some bullshit. I would take a hard look at who I’m accepting free candy from, if I used it.

That’s really smart. That way if I ever figure out the command to exit Vim, it’ll behave the same as my current method (powering off the PC.)

This means that using most Linux apps are something to be avoided for most Windows users, making the OS base mostly unusable for them.

I take your point. And this was very much the case for a long time.

But it’s worth pointing out that Gnome and KDE are both done, now.

I haven’t been forced to reach for command line to change something - anything - on either of my last couple of Linux installs.

Edit: I almost didn’t notice, but it feels worth celebrating and raising awareness.

they’re mad that Linux devs regularly stop creating P&CI features, instead opting for CLI with no P&CI equivalent action.

I’ve never seen this?

It’s typically a completely different developer who creates the CLI first, and then one of us adds a P&C after.

So if something is brand new, sure there might be no P&C, yet.

I promise There’s no conspiracy to not have nice things. Haha.

Installing software on the command line is often a nightmare

In my experience, installers are often a nightmare.

For me, GUI vs CLI have about the same failure rate (for their operating system).

But I appreciate that the CLI version gives me a message I can search for instead of a “fuck you buddy” pop up box with an “ok” button.

Edit: There’s one case where I have a much harder time with CLI installs - when there’s only a CLI “installer” available. I don’t blame the CLI for that, I blame the person who shares seven CLI commands instead of writing an installer.

You may want to check out Ghost Commander and it’s many cross platform clones. They include a nice mix of graphical and batch command tools.

Shit. I wish we had that option (dragging files between folders) on Linux. Maybe someday.

(This is a joke, about how it feels like a lot of folks with strong opinions about Linux haven’t tried Linux in a long while.)