People say it because it was a Windows limitation, not a computing limitation. Windows Server had support for more, but for consumers, it wasn’t easily doable. I believe there’s modern workarounds though. The real limit is how much memory a single application can address at any given time.

Immediate recommendation with KDE: your Windows key and the ~ key pressed together will bring up the ability to set snapping zones for windows. Very helpful tool, especially if you were a fan of “FancyZones” in Windows

A lot of folks will recommend Mint as the first option, since it’s pretty straightforward and will feel a lot like older editions of Windows. Personally, I use Fedora Plasma, because it feels like what Windows 11 should have been, and it supports just about everything I’ve thrown at it. It’s got pretty broad support, so it’s easy to get into.

I don’t feel like this is a terribly recent attitude. It’s definitely one I’ve encountered repeatedly over a decade or more of dipping my toes in the pool. It’s not incorrect in a lot of circumstances, but it’s very difficult to find support when no one wants to help you improve. There’s always been a significant degree of ego in Linux user communities.

That’s exciting. It looks very clean, but until it has the tv remote support aspect I think it’ll wait

Flatpaks are basically containers, allowing applications to maintain their own dependencies separate from your system. It’s similar to a Windows program shipping with its own precompiled DLLs, helping prevent dependenct conflicts when you go to update something you installed with pacman or yay.

Seems to depend on the flavour of Android. What version/brand do you have? I know my Pixel asks first unless I allow it more generally.

You may be looking for the “Instant Apps” settings though. Searching “links” in your Android settinbs should provide a similar result regardless what brand of phone you have though.

Arc support was added after release to Linux Kernel 6.2 and it’s steadily improved since. Older Linux distros, or “LTS” oriented distros that favour stability may still not have support for them. I know Unraid was very slow to pick up on it and I had to settle for passing the pcie device through to a VM to get it working. Intel is keen to made these viable though, and I love having the AV1 encoder from my A380.

That’s not an equivalency. From written paper to typewriters and then to computers, writing has remained a product of the author. A typewriter repair shop would transition from mechanical to electronic typewriters and potentially then to computer repair. This is because it supports an evolving technology.

An author cannot transition to becoming a machine, because they cannot author what they don’t write, but a publisher can continue to publish anything that would make them money. So when human experience is boiled down to nothing more than the probabalistic order of the words written by authors who gave no consent to have their work absorbed and mutilated by an LLM, the only winner is a publishing house seeking cheaper labour than the human.

That one sounds squarely on Nvidia. Any driver that uses undocumented workarounds to gain kernel level access or utilizes an access loophool for system hooks is a bad driver. I’d assume Debian, or likely more accurately the Linux kernel itself was updated following some matter of CVE that Nvidia was quietly abusing.

Frustrating, but a good example of why those kinds of proprietary drivers are such a nightmare. You really just don’t know what techniques they’re using.

Biggest difference is that wormhole will pass traffic between devices on different networks as long as both are routable. So it’s not limited to a local network connection.

Ah, I see where I got confused. Yeah, CGNAT isn’t very common around here. I don’t think I’ve ever run into an ISP that uses it. I can see how that complicates things.

You really don’t though. I use wireguard myself under the same scenario without issue. You just need to use some form of dynamic DNS to mitigate the potentially changing IP. Even if you’re using Tailscale you’ll still need to have something running a service all the time anyways, so may as well skip the proxy.

Oh yeah, at the time there was no support for my current registrar. It was a fun enough project to put my own script together anyways.

This is probably not what you’re looking for, but I found registering a cheap domain name and using a dynamic DNS script that checks every hour or so against your public IP to be a good way to mitigate issues. It also depends on your ISP. Mine typically only renews upon a reboot of the modem or a new PPPoE authentication.

Others have also suggested Tailscale, and I think that’s also a worthwhile option. It’s a pretty easy thing to set and forget, working like any oher VPN client. This is the least complex option to navigate, and if Plex was the only service you were forwarding then it’s likely the best option.

I use Wayland exclusively, but unfortunately I don’t think I have an answer for you since I’m not entirely familiar with this idea. Is your concern just for the configuration of a universal set of hotkeys configured within the compositor rather than a desktop environment?

I wasn’t aware that x11 facilitated this. I’d have figured keyboard mappings are abstracted from the compositor and left to the DE to handle, aside from core binds that allow dropping back to tty

I think the complaint is that it got linked in the linux community? Idk

What would be the difference between Fedora Kinoite and this?

Can confirm. Currently running everything on there through Proton unless there’s some outstanding issue

Recommendation: use Heroic instead for Hoyo titles. It’ll launch with Proton/Gamescope and it’s far more reliable.