Yep, I really hope a future will become reality where Adobe has some competition and/or an incentive to port the suite to Linux. I just can’t help but cheer on the sounds against Stockholm syndrome. So much of these “it doesn’t work on Linux” is just the company intentionally trying to prohibit integration with open systems (looking at you HDMI forum). In the end I agree, though, when giving advice, it’s best not to assume the “only gaming” use case.
From my experience it’s still a common misconception and I think it’s the largest potential group that can switch. Sucks that your usecase is unsupported, though. Just out of interest, what software can you still not run?
It’s been a while since I’ve watched it myself, but remember them going into the ownership structure.
https://www.youtube.com/watch?v=hNZy603as5w
There’s basically no way for them to not make it a subscription model.
This is a pretty interesting counter example: https://www.eteknix.com/running-yuzu-on-switch-gives-you-better-performance-than-native-gaming/
But, as others have said, exceptions confirm the rule.
Ever heard of IPFS? I really hope that will take off some time.
I think some more info is necessary on the DNS configuration. You’ve made an AAAA type record pointing to the ipv6 address of the server (not the router)?
Been running Wayland for 5 years on my development laptop (sway, Intel GPU, blacklisted the nvidia gpu). At the start I’ve had a couple of issues, nothing too bad. Haven’t had any issues for over 2 years. Switched to Linux on my gaming PC about a year ago, KDE plasma on Wayland but do most of my gaming from a steam gamescope session. Very happy overall with Wayland, glad it exists. Sharp text on a fractionally scaled display for reading code was just too compelling at the time and it only improved.
Maybe Firefox, Thunderbird or Steam are running in XWayland and that causes different behaviour between them. Just guessing.
The Dutch student loan program is gonna be in a lot of trouble… (Dienst Uitvoering Onderwijs)