Kinda insane how many people in a nominally open source community are defending this guy for switching to a proprietary license. If DuckStation gets shut down then I say good riddance. It is not the only PS1 emulator in town and I will not miss the endless flow of Stenzek-related drama.
You mean VHI bug? Says there are still 36 15 minute bugs.
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).
Well, Steam and Proton both already run on top of FEX or Box64 on ARM Linux, but it’s nice to see an official effort from Valve.
Also, does ARM still have better battery life when all of the machine code has to be translated from x86? That adds a not insubstantial amount of CPU overhead, which does hurt battery life.
And perhaps most importantly, is there any ARM chipset out there that can deliver performance on par with the Steam Deck’s CPU (even after factoring in the overhead of the x86 JIT) at a viable price for a Steam Deck successor?
Obviously. ES6 isn’t out yet. The point is that there are many things ES6 could improve over Skyrim if they tried.
Dunno, I think I prefer patents. Unlike copyright, patents usually last a flat twenty years. Copyright expires either after 95 years or 70 years after the death of the author, which is ludicrous. Both are constantly abused, but at least patents expire in a reasonable amount of time.
Unless they changed it, mobile Firefox is locked to a limited set of extensions unless you:
You’re also unable to use about:config unless you’re using Nightly (or maybe Beta). So Nightly is really the only version worth using since it doesn’t have nearly as many artificial restrictions as the stable version does. This is also true to a lesser extent on desktop where you have to use Nightly to install unsigned extensions.
You also can’t open any offline HTML files for whatever reason and on devices with very little RAM (like 2GB) Firefox isn’t viable, but Chrome-based browsers work mostly fine. Firefox is still the best mobile browser though, mostly because it supports extensions at all.
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.
I see. Will avoid, then. I don’t like lucid dreaming, always wake up right away. Whenever I notice I’m dreaming it becomes hard not to notice that I’m in my bed and that I can feel my covers and by that point it’s all over, so whenever I notice I’m dreaming I just cut the crap and open my eyes for a couple of seconds to wake myself up and then close them again so I can get back to proper sleep.
Is this really useful? Like, is this something people ever need to do? I don’t do lucid dreams very often, but the rare times a dream has lead me to the thought of “hold on, am I dreaming?” were basically immediately answered by just, uh, vibes, I guess? Like, it’s always just been instantly obvious that I’m dreaming the moment I’d start questioning it, no tests necessary. At worst I might have to try to remember what I did the day before and what I was supposed to be doing that day and see if that is at all compatible with the scenario I’m dreaming about, which it usually isn’t.
Why do you believe a “nutrition brick” would be at all more appetizing than the things described in OP?
Esperanto has grammatical gender.
Do you… not know how multi-licensing works? You can use the project’s code under the terms of whichever license you prefer, you don’t use all three at once. Simply putting the AGPLv3 does remove unfair restrictions, because it means you don’t have to use either of the proprietary licenses the project was previously only available under.
I don’t follow. ElasticSearch was only available under proprietary source-available licenses. Now, it’s also available under the AGPL, which is open source, meaning ElasticSearch is now open source software. What part of this is deceptive or contradictory?
Uh, no. Not the majority. Not by a long shot.