Hm? Wayland has VRR.
Hm? Wayland has VRR.
FIFO and commit timing are big for gaming. IIRC the lack of those protocols was a big reason why devs didn’t want to enable Wayland support for SDL3 at first.
Man, this guy does not give up. Respect, honestly. Hope for the best this time.
try disabling any krunner plugins you don’t need. that should make things faster.
Sketchup has always worked pretty well with Wine. It’s always just been installing a couple of things with winetricks (like vc runtimes) and then it usually works fine.
Uh, no. Not the majority. Not by a long shot.
What problems do you anticipate? Wine, which Proton is just a modified version of, implements file dialogs. If it didn’t, just about every application that isn’t a game would be broken. Needing to open files is pretty ubiquitous, after all. You need file dialogs for that.
It isn’t significant. Wine already supports the vast majority of MediaFoundation codecs with GStreamer. This is just an alternative backend that uses FFmpeg instead of GStreamer. GStreamer already has an FFmpeg plugin, so this doesn’t add any new codecs to the table. It seems there’s just a long term plan to move away from GStreamer for whatever reason.
Wine’s MF support used to be much worse, which is why Valve had to do their workaround shader hack. Not sure what exactly the current status on that is, but I do know things like mf-install or Proton-GE are rarely if ever necessary anymore, even with non-Steam games (which I have plenty of).
I’m surprised you could even run a Linux distro with X11 and KDE1 on 8MB of RAM.
Qt1 came with two default themes. One of them mimicked Win95 and the other mimicked Motif. KDE1 defaulted to the former in order to look more familiar. To this day, the “Windows 9x” theme still ships with Qt and can be selected on any Plasma 6 install. Starting with KDE2 they started using their own custom themes for everything, tho.
GNOME 1 actually looked very similar, which isn’t surprising because its main goal at that point was to offer a replacement for KDE that didn’t depend on then-proprietary Qt. GNOME 2 and KDE 2 is when they really started building a distinct identity.
Yeah, I mean Google caring about Linux isn’t exactly breaking news. We knew that already. Android and ChromeOS both exist and as web company they kinda have to care about the OS that by and large runs the web. But this is Phoronix and they’ll make articles about anything as long as they think as it’ll get engagement. “Chromium” and “Wayland” are pretty good buzzwords as far as that goes, thus this article. My point is more so that maybe it isn’t productive to have every acknowledgment of Chromium’s continued existence be overwhelmingly negative regardless of context.
This isn’t something to complain about, IMO. Chromium is a popular app and it is a good thing to see work on supporting FDO protocols and improving Wayland support. I prefer Firefox myself, but it’s nice that Linux support isn’t just an afterthought for Google either and more importantly it trickles down to the countless apps on Linux that depend on Chromium in some form (usually through Electron). I personally use several, including but not limited to Slack, Discord, r2modman and VSCodium.
especially considering KDE already has an application with almost exactly the same name for the same purpose https://invent.kde.org/utilities/alpaka
color management is by no means “mainly used” in gaming
They attempted to add opt-in telemetry a few years ago and people lost their shit for some reason. They didn’t merge it, but the FOSS community’s “fork first ask questions later” attitude kicked in anyway and multiple forks popped up while now the original project has permanently been labelled as spyware, which is fun. Fun fact, KDE Plasma actually has opt-in telemetry. Dolphin, Kate and a few kdepim apps also do. Plasma also has opt-in automated crash reporting, which is particularly evil. Y’all better uninstall them right now. I mean, what if you accidentally opted in, or something? Anyway, not a fan of hostile forks unless someone can actually prove the original project has gone to shit.
you don’t actually have to do that. for the most part you can just run everything in the same prefix. it’s what I usually do.