deadcream

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.

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.

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).

They already did (I’m not sure if it is already released to user but code is in Chromium).

Microsoft fights very hard to keep governments across the planet use Windows and other Microsoft products (it’s very lucrative market because of corruption and the fact that government regulations on what their employees must use are slow to change once established). And they have very close relationship with USA government specifically.

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).

I think it’s just this feature is so big that it requires months of focused uninterrupted work by a dedicated team of engineers - something that’s unlikely to happen in a project that relies on volunteer effort. Microsoft could do it because MSVC is developed by a dedicated team of developers working on it full-time (and paid for it). Clang probably was just luckier than GCC and there were people in its community passionate enough to drive this work (still its modules implementation is still less complete than MSVC AFAIK).

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.

That’s how they do it. They send their “proposal” and immediately implement it in Chrome (with work on that being started long before “proposal” is made public obviously). Then they start using it on their own websites (with compatibility for now) and start propaganda campaign to push webdevs to use it too (which they do of course). Then they start complaining that other browsers’ developers are slow to implement this new “standard” (at this stage they won’t call it a “proposal” anymore) and are “stifling development of the web” or being actively malicious because they are jealous of Chrome or something. Then compatibility mode on their websites is first subtly broken so that users once again will witness how Chrome is superior browser and then removed outright. Boom, we have a new web standard!

I don’t use it myself, but I don’t have a strong opinion on that. My beef if with deduced return types, especially with templates. It is typical in modern C++ code to see such function:

template<typename ~whatever~>
auto foo(~some arguments which types are deduced from nested templated conditional using declarations that you don't understand~) {
    return ~call to other template function that's 10 levels deep and is also conditional on properties of template parameters with some ifdefs for fun~;
}

That makes it absolutely impossible to figure out what types function takes as parameters and what type it returns until you hit 10-page compiler error that will explain everything (which is also will force you to read through implementation details of this function to figure out how to fix it). And often IDEs can’t help you either.