If it doesn’t even boot from the USB stick then it’s probably a hardware issue.

That’s the problem of most general-use languages out there, including “safe” ones like Java or Go. They all require manual synchronization for shared mutable state.

They are trying to make money to stay afloat. Postmarketos is a community project so it’s not comparable. And neither Purism nor Pine64 seem to be huge commercial successes just like Jolla, though they seem to be doing a bit better.

They have been owned by a Russian state-owned telecom corporation for a few years until recent events (Russia currently tries to push Sailfish OS fork as its “russian-made” mobile OS). Original Finnish management has split off to a new independent company with the same name last year, and this looks like their last ditch attempt to continue existing. I don’t expect they will last much longer (the reason why they were bought by Russia in the first place was that Jolla failed as a business).

Qt 6 has been out for more than three years now.

It’s not ready yet.

The protocol for apps/games to make use of it is not yet finalized.

Gconf was text though (well XML actually but not binary).

Well it could be that the application uses some Qt functionality that does nothing on Wayland, and the developer may not be aware of that. Though it could be challenging to fix this in a cross-platform way.

BTW those warnings about requestActivate should go away when those apps migrate to Qt 6.

You can report it to developers of an app which prints these warnings. It could be a bug where some functionality doesn’t work as expected on Wayland.

It’s the standard location for all apps (actually it can be overridden by environment variables and ~/.config is the default value). However like many things in the Linux world it’s not enforced. Some apps (especially console utilities) don’t respect it but most use it.

What exactly do you expect users to do when they see “WARNING: what you are doing is unsafe” message? Cause the only outcome I can think of is that they won’t install themes at all.

It is scalable but the icons are still drawn against the virtual pixel grid. If an icon is designed to be perfectly pixel-aligned when rasterized at a certain size, then rasterizing it at 1.25 of that size will cause small distortions if it contains small elements (such as 1 px width lines).

There is a checkbox with a very confusing name in the task manager applet’s settings that does just that. I can’t remember its name just now (something about separated launchers. It’s “Combine into single button”. Nope, it’s “Keep launchers separate” and it’s indeed needs restart).

Please, someone tell comrade Stalin Xi that this is all just a terrible mistake!

I fear that at these resolutions we will discover that UI frameworks are not really scalable in terms of performance

Even “real” fractional scaling in Plasma with Qt 6 is not much better. Text will look slightly sharper, but icons are still blurry. There is no way for them to look sharp with 1.25 scaling since they are drawn with a pixel grid in mind. Unless you invent some way to stretch svgs so that their individual elements and spaces between them retain their integer-ness while the scale of the whole image is fractional.

The only other solution is monitors with 300+ PPI where blurriness is simply not noticeable (that’s the way Apple went).

It looks mostly the same as XML views but some components look and behave wildly different for no apparent reason (tooltips are one of those).

I have given up on the fight a long time ago. On the desktop the only line I draw is that the app must respect system font configuration and use system-provided file dialogs.

Some distros (Fedora at least) have debuginfod integration,meaning that gdb will automatically download debuginfo files. The downside is that it will take a while for download to finish (for the first time at least) since it gets symbols for all linked and loaded libraries recursively, and it will take a few gigabytes in ~/.cache.

JS by itself is very fast (it’s one of the fastest dynamic languages). It’s interop with platforms APIs that is slow, at the fact that each React app spins up its own instance of Chromium also doesn’t help.