Either native or not at all. The way proton sits in the middle leaves Linux with all the complaints when it goes wrong. Not Linux's fault. It's people like you that are to blame for putting Linux in a situation it should never have been in. Linux does not need games, anyway. Games are for children.
Great, you don't use it. I see it in use all over in my company, and in a couple others. It is an important core functionality. That the wayland devs ignored the use case at all to the point of other devs writing wapipe to overcome their screw up is huge.
It was more attrition by age. New devs came in and didn't fully understand it. The XFree86 vs Xorg war only made that problem worse. Those who came later didn't understand it well enough to continue supporting it. Now you've got young devs not understanding why things are important to its design, and of course, they want to rip it all up and start over. They haven't yet learned the lessons of what made the design choices important.
Don't remind KDE of their KDE 4 past in their official communities. @Bro666@lemmy.kde.social, one of their mods, is suuuper sensitive about it. He'll say that mentioning it is rude, and if you dare stick up for factual statements, he'll ban ya. Don't give feedback, either. Anything other than praise he calls rude and tells you to go code it yourself. Real piece of work, that one.
RandomLegend_dbzer0 that comes with the dbzer0 site. I've tried them all, but often I can't open the sub replies link. In all of them it just spins when you click it, you never get to the comments. Had the same problem on two other lemmy instances and various themes in the past. Only thing I've tried that works is Voyager on my phone.
Because it discourages native Linux game development for something 'good enough' using a windows compatibility layer that really is just a large hack. That's why I care. Games for Linux should be made naively for Linux, to bolster the Linux operating system. When wine/proton fails, people confuse it with being the fault of Linux, when it's not. It is the fault of running software not made for Linux to begin with on a compatibility layer. Those problems unnecessarily tarnish Linux. It's wrong, it really shouldn't be allowed, and I'd be happy to see Wine/Proton sued out of existence to prevent it.
Ok, lemmy isn't showing me the full context of our thread anymore... So I'm with you on the trauma of those terrible creations. Where were you going with it?
When your games have an issue, don't blame Linux. Don't even mention Linux. It'll be your own fault for using a compatibility layer (Wine/Proton). The games are written for Windows, they shouldn't get any of your money.
Remote desktop is not what I'm talking about. Remote applications. Individual applications. Remote desktop is way too much when you want individual apps and for them to respond to your local window manager and copy & paste buffer.
If only. Took a long time to trust KDE again after their disaster called KDE 4. Worried as hell now that they intend to remove functionality in KDE 6, as well as making new wayland only features. And if you dare remind them of KDE 4, they get their pants in a twist.
Remote full terminals, not just remote shells, are invaluable. Remotely displaying old HP Openview. Remotely displaying tn3270 to access the mainframe payrole system that only allowlisted the bastion host for security. Remote displaying legacy X apps, like my engineers migrating ancient flight control documents from Interleaf to QuickSilver, other Motif applications. There are industries still needing and using this stuff. Hell, there are still Apollo systems around running X11R4 and rlogin running around in server closets on token ring because of data that could never be migrated. Congrats on 42, you're still young.
The performance isn't the best, when compared to RDP. Protocols like RDP can take shortcuts by treating it more as an image then a fully remote rendering, like image compression techniques. For tunneling an X-window over SSH, the compression option you have is with the connection, itself. Using say, ssh -CX or ssh -CY allows ssh to compress the connection for better performance, but that compression able to do lossy image compression. The killer will be latency. If it's over a highly latent connection, like a WAN or satellite, it will be rough. But on a wired lan, or decent local wifi, it's pretty all right.
Either native or not at all. The way proton sits in the middle leaves Linux with all the complaints when it goes wrong. Not Linux's fault. It's people like you that are to blame for putting Linux in a situation it should never have been in. Linux does not need games, anyway. Games are for children.