Then don’t ever get rid of your own place, so you can prove you’ve only been dating, not living together.

You mean, besides being chromeos? ;)

And Mint because Gnome (shudder)

This wasn’t just ignorance, this was willful ignorance.

I suggest a filesystem that supports taking snapshots in the future. It’s a lifesaver for moments like these.

When distros make it the default DE, that’s forcing it on them. No different then Microsoft bundling a specific browser. I also disagree that it works well on desktops. It lacks features, and tweaking it to resemble and behave like a more common desktop design is cumbersome.

Gnome. It’s made for touchscreens, but forced on desktop users.

Never give power to those who seek it.

I would, but that thing is happening again where I’m not seeing other comments… just the count of comments. WTF lemmy?!?

Wait what? I’m no fan of Wayland, but what you just said, I’m afraid, is all wrong.

1. Wayland, although being around for over a decade, is the newer protocol. The older protocol would be X11.
2. Pipewire is also the new kid on the block, for audio. PulseAudio would be the older one being replaced.
3. WINE is a Windows compatibility layer or wedge. It stands for Wine Is Not an Emulator, if I recall.

Wayland seeks to provide a newer display standard, as I keep being told (forcefully and repeatedly) X11 is not sustainable… There’s a lot about that we don’t need to rehash here, but long story short, In with the new (Wayland), and sooner or later, out with the old (X11).

Pipewire is meant to be a replacement for PulseAudio, and near as I can tell, quite backwards compatible.

WINE is to run Windows application on Linux. Like many Linux applications right now, it is being updated to support Wayland (I believe that’s well underway already) and it already works fine with Pipewire. WINE will work on X11 and Wayland.

Lastly, what do you mean by weaker systems? X11 is weak when it comes to being security conscious. Part of Wayland’s mission is to address that by being far more secure by default. Pipewire, while maintaining backwards compatibility, is able to do more things, as well, than the original PulseAudio.

I’m sorry, I found your response confusing. Arch is a Linux distro, I know flatpak is available for it. If there’s a bug with flatpak, I would expect it to be pretty much the same across most GNU based Linux systems. My question, however, was why use flatpak on Arch Linux at all, as the AUR has pretty much everything including the kitchen sink… unless you are developing flatpaks, I guess, in which then it would make sense to me.

You don’t owe me an explanation, it just sounded odd to me to be needing flatpak when there was AUR, was all.

Flatpak on Arch? Is what you want not in the AUR?

Oh my god, this. Especially on the external monitor.

Wearing a “hat”!

RDP is not a replacement for individual remote apps, btw, just saying. RDP is a full remote desktop, like VNC.

It’s more incestuous than that… It’s a Motherboard with a Daughterboard. 😲

Sounds like an act of civil war. Spank them… spank them hard, daddy.

Kernel 0.99pl13, Slackware, 386-SX 16. Started as an obsessive hobby, became a career.

All these laptops make a circle… All these laptops make a circle… ;)

I will never install a Linux desktop without a snapshotting root filesystem ever again. Nvidia driver updates, /boot getting too full during kernel or driver updates, a bad update of pipewire half a year ago, and more I can’t remember. Was always able to boot to previous snapshot of the OS, and address whatever it was. Some ZFS here, some BTRFS there… and my small fleet of Linux desktops are as easy to recover as any immutable OS. Better even, because snapshots allow me to pull individual items or things between states easily, too.