deadcream

Lada doesn’t really exist anymore. Before 2022 it was just assembling cheap Renault cars with Lada branding (and actually owned by Renault). Now it’s nationalised and assembles some obscure Chinese cars (or plans to. Not sure if they managed to set it up yet).

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.

If they can built space rockets that can carry payload to orbit, they can build ICBMs. First space launchers were modified ICBMs after all.

It’s a feature-rich text editor with LSP support. I suppose you could use it as a simple IDE, though I haven’t tried it.

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.

Maybe it’s a corpo thing, how big is your company?

DLSS is upscaler. Game is rendered at lower resolution and then image is upscaled in a bit smarter way than simple “stretching”.

iPhone 15 Pro owners are using it wrong

• Apple

This happens on most Android phones, including my Google Pixel with 8gb of RAM. I noticed that it starts doing this when battery drops below 50%. Which is weird because it surely takes more resources (and thus drains more battery) to cold start an app every time instead of just keeping it in memory (provided that app doesn’t do anything nefarious in background which is easy to detect). There is plenty of RAM for that.

It seems to be fully backwards-compatible with standard JPEG. I.e. image viewers will that don’t support newer formats will display it as if it was a JPEG file with SDR colors.
Also, HEIF/HEIC is patented format that you need to pay royalties for. Open formats are obviously superior and there are multiple ones that support HDR (there is also open variant of HEIF that uses AV1 encoding but I don’t know whether Android or iOS support it).

It’s also the home of people being drafted (even more so than for political elite of the country). If some of them want to get the fuck out (yes, from their home) then those thay have elected shouldn’t have the right to force them to stay and die.

Not only Google services. If you want to make a phone you need to buy SoC from Qualcomm or MediaTek and all the drivers for it are proprietary (often including Linux kernel modifications). Sure you can technically make your own but it’s impossible for 99% of phone makers.

Some apps can’t even be disabled (including via adb).

Well, yes, it’s a business decision. Google wanted to push their Chromecast devices so they made them use proprietary Google Cast protocol and removed Miracast from Android (both phones and TVs). They later added Chromecast/Google Cast to Android TV but it is still not supported on other platforms. Samsung on the other hand had their own TVs which don’t use Android TV so they added Miracast back to their phones and removed Chromecast so that their consumers would buy Samsung TVs.

Now it looks like it’s hiding something.