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.

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.

Generations Vi, VII and VIII all had fewer than 100 new Pokemon.

Why do you believe a “nutrition brick” would be at all more appetizing than the things described in OP?

Esperanto has grammatical gender.

Uh, Cinnamon does not need a compatibility app to run Qt apps. No desktop environment does. You mostly just need to be X11 or Wayland compliant. The same is true with GTK.

MV3 doesn’t make adblockers impossible, only less effective. It’s important to note that MV3 has changed a fair bit since the initial controversy and isn’t quite as limiting as it used to be. The fact that adblockers will lose some functionality at all is still a dealbreaker for me and many others which I thankfully won’t have to deal with as a Firefox user, but it isn’t going to kill adblockers on Chrome and most users will probably just install an MV3-compatible adblocker and move on with their day.

uBlock Origin’s developers don’t seem to want to make a proper MV3 port, which is fair because they’d probably have to rewrite most of the extension, but they did create the far more minimal uBlock Orgin Lite, which a lot of people have taken to be an attempt at porting uBlock Origin to MV3. It isn’t that. On top of MV3’s limitations, it also makes the decision to work within these self-imposed restrictions:

• No broad host permissions at install time – extended permissions are granted explicitly by the user on a per-site basis.

• Entirely declarative for reliability and CPU/memory efficiency.

These aren’t MV3 limitations, just a thing Gorhill decided to do. See the FAQ. You can get much closer to uBlock Origin within MV3’s constraints than uBlock Origin Lite does. Right now, the best option appears to be AdGuard, which has been making a true best-effort attempt at porting their adblocker to MV3 pretty much since the announcement.

Er, yes. It’s one of the main features being introduced in 3.0. I don’t know why you would just assume they’re not adding it without looking it up. It made quite a bit of noise when it started being in the works.

Basically everywhere I go on Lemmy you’re there spouting ignorant bullshit, garbage takes, rage-bait and misinformation. You’re inescapable. This is the perfect example. You know what you’re saying is wrong. You know you’re being dishonest. Do you wanna know how I know? Because I literally told you as much less than two weeks ago when you tried spreading the same lies. But you didn’t care back then and you still don’t care now. The only thing you seem to care about going by the other things I’ve seen you post is pushing your favorite projects, and you will use all of the arguments available to do so, including the ones that you just entirely made up. You think LadyBird is the better project and are trying to spread the belief that Servo is dead to make others buy into the LadyBird hype further. But, of course, Servo verifiably isn’t dead and in fact the Servo team writes up monthly blog posts detailing their progress, which show the project developing at a healthy pace. And to top it all off, when these facts are pointed out to you, your only comeback is “means nothing”. Clearly you’re not the kind of person to let facts tie you down.