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.

Google-certified Android TV devices aren’t known to receive security updates either.

Kaspersky is closely tied to Russian government. The dude himself (founder and CEO) has a government position as one of Putin’s advisors or something. Also he believes that anonymity should be purged from the internet, and every user should be personally indentified, enforced by the government. In the name of “security”, of course.

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.

Russia already has national root TLS certificate that’s must installed on all devices (basically government-mandated MITM). The next step is to start severely throttling (and optionally blocking) TLS connections that don’t use it. Some popular foreign sites like Google can remain functional by replacing their certificate at ISP level (all ISPs are already controlled by the government).

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

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!

Now it looks like it’s hiding something.

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