Systemd isn’t “correct” what does that even mean? If you don’t agree with the standards and practices of the systemd project, that’s fine, but don’t act like there is some golden tablet of divine standards for system process management frameworks.
I wasn’t making an argument that systemd is perfect or that other frameworks like runit are inferrior. My argument was that I’ve been running a lot of Linux servers and desktop systems for years and I’ve never experienced the “huge stability problems and nightmare daemon management” that multiple systemd haters claim I will inevitably experience.
Maybe I’m incredibly lucky, maybe I’m not actually getting deep enough into the guts of Linux for it to matter, or maybe systemd isn’t the devil incarnate that some people make it out to be.
And also, free software is a thing. So I absolutely support and encourage alternatives like runit to exist. If you want your distros and servers to only use runit, that’s totally fine. If it makes you happy, or you have some super niche edge-case that makes systemd a bad solution, go for something else, you have my blessing, not that you need it.
From what I’ve heard, it’s more common in Europe and parts of Asia. I’ve personally never seen significant Linux use of any kind in the IT environments I work in, sadly.
It’s all Microsoft product stacks, the servers, the endpoints, the cloud environment, all MS. Sometimes their Hypervisor would be VMWare, and their NAS was a Synology. But other than that, basically all Microsoft garbage.
I did work at one place that had a fair bit of Linux infrastructure. The lead network architect was a hardcore Linux/FOSS grognard. Really smart guy and was fantastic at his job, I learned a lot from him. But the only reason that company had Linux servers and a few FOSS implementations was because that guy insisted on it and managed all of it himself.
I also worked at another place where one of the older IT guys had installed a handful of SUSE thin clients at various locations for employees to clock in with. But right after I started there, management wanted me to switch them out for Windows thin clients. I pushed back but they insisted, so there went the tiny bit of Linux at that company.
I run a bunch of Linux servers, multiple desktop instances, manage multiple IT clients, and took my first Linux certs working with Systemd management, all for years now.
But I’ll be sure to switch away from systemd when it becomes an issue…
In KDE Plasma, Super + T brings up a built in tiling feature. It’s super basic, but allows you to set static window snap zones on any display.
Each zone can be split horizontally or vertically, and you can adjust the zone-gaps to the exact pixel you want.
It’s not dynamic as far as I know, but for me it’s all I need.
Once you go back into regular desktop mode, you can use the zone snaps by holding shift while you drag a window. Releasing the window while holding shift will snap the window into the current snap zone it’s closest to.
ZorinOS. I tried to install it on my spouse’s computer with all modern, well-supported AMD hardware. Had nothing but problems, to the point that the computer was barely usable. WiFi broken, GUI was laggy, repositories were buggy. When I finally got the system somewhat stable, I didn’t like the interface at all. Styles were bland, icons dull, everything just seemed clunky and awkward.
For a distro advertised as a beginner-friendly and pay-for-polish system, I was very dissapointed.
Might have been a fluke, I don’t think my experience is standard for Zorin, but it was a really terrible first impression and I never suggest it to Linux-curious folks. Mint or Vanilla Fedora are my go-to for newbs.
Arch was great for teaching me about Linux. It was rough, I completely borked my system about 3-4 times in the course of about 10 months lol. But it taught me valuable lessons on how to fix a destroyed system, how to use Timeshift to rollback changes, how to patch drivers and specific system packages, etc.
Ultimately, it was the constant fiddling that got me to go away from Arch and towards Nobara for my main gaming PC. I just wanted an OS that was stable, had great gaming performance, and didn’t require me to install a bunch of obscure packages and tools like Arch needed to get certain things to work.
Nobara has been fantastic so far and is probably my go-to distro recommendation for folks who plan on gaming hard on Linux, their pre-included kernel patches and utilities like Protonup-QT are awesome for gamers.
I installed LMDE on my work IT laptop recently and overall I like it. Have had a few annoying bugs because of Debian’s old packages, but everything is ironed out now and it’s great. Something stable and basic that gets out of the way for me to do my job.
Yeah, but what if you needed to haul a team of volunteers to do disaster relief with a 9,000 pound trailer filled with water and food and then use the empty bed to haul debris away while rescuing survivors from the flood waters?
Nyfure is right. Wayland support is experimental but has been added to Rust Desk since earlier this year.
I haven’t tested it on Wayland myself, and remote login isn’t yet supported according to their GitHub documentation, but if you just need a reliable way to provide remote support to your fam, it’s a really solid option.
Wayland is quickly becoming the standard, and Rust Desk seems to be on that train which is good. I wouldn’t be surprised to see full Wayland support or close to it by the end of next year.
Also, I just use the .appimage file and it works fine for me. Just make sure to set it as executable with chmod +x or in the file permissions tab in your GUI.