Sure, it’s hard to craft a perfect solution. However the status quo for a long time was that applications were doing it themselves. And Wayland took it away without providing a replacement.
Sure, it’s hard to craft a perfect solution. However the status quo for a long time was that applications were doing it themselves. And Wayland took it away without providing a replacement.
I had been led to believe that one of Wayland’s strength was solving the correct window coordinates save-and-restore problem. Does someone know what happened here?
It’s literally the opposite. Windows aren’t allowed to position themselves on Wayland (because it’s unsafe or something). Window state save restoration must implemented by the compositor itself. Not sure about GNOME, but KDE doesn’t have that.
Dial the Gate. Series of interviews with people involved in making of Stargate TV show (not just actors bit people at every level). It’s over 200 episodes now.
Well GTK does not have theming anymore, though it still needs some way to configure fonts and icon theme.
Does it really matter? It’s the usual corporate intrigues/power struggle/backstabbing/whatever. Just for some reason leaked into public view instead of being behind the scenes like it’s normally done, probably because someone is stupid.
Low effort tickets are ignored because they are bullshit.
High effort tickets are ignored because devs are lazy and can’t be bothered to deal with complex and boring issues.
Well, at least that’s how I roll as an open source developer lol.
It’s still not enough time for KDE devs to fix all major issues with Wayland. It requires at least another two years in the oven.
I wonder if they consulted Plasma devs about it. Sure they said that they aim to make Wayland ready for Plasma 6, but it didn’t sound like it was an actual plan for 6.0. After all they got their hands full with Qt 6 porting, and there are still major roadblocks with completing Wayland support, while 6.0 is about to have its alpha release already.
Knowing Fedora devs however, I suspect they didn’t. They switched to Plasma Wayland by default several Fedora releases ago, when it was in no way ready. I guess I will switch to a different distro when this time comes.
I’m fine when music content appears in Youtube recommendations, but videos in Music recommendations is absolute cancer.
I’m confused on how mobile clients work with Fediverse. Do they work with larger “threadiverse” like Lemmy and Kbin themselves or do they access it through specific Lemmy/Kbin instance? If it’s the latter, does this mean they use Lemmy-specific and Kbin-specific APIs?
Only if you use 15 years old distribution. Linux actually drops support of older hardware faster than Windows, it just doesn’t happen consistently. Old drivers are maintained by volunteers so if someone wants to spend their free time on a driver for 25 years old hardware then it will work. But the moment that single developer disappears or stops caring then this driver is booted from the kernel fast. Supporting old hardware isn’t the goal of Linux unless someone make it their goal (and core developers don’t care either way as long as it’s not their job).
He was pretty clear in Quran on that topic.