tl;dr:
std::unordered_map is one of the worst ones, boost::unordered_flat_map and absl::flat_hash_map are one of the best.
deadcream
joined 9 months ago
It's not even about waiting or patience. I'm not a teenager anymore, so I don't have as much to play games as I used to (and I have now other interests too). I have so many great PC games in my queue I literally won't have time to play them all until I die. The queue only gets longer with time. So what if I can't play some console exclusive? It's just one game in the long list of games I won't get to play and I have no problems with that.
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.
Owntracks link is broken.
Because that's not an investment, it's a donation.
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).
Variable names shouldn't need comments, period. You don't want to look it up every time this variable is used in code, just to understand what it holds. Of course there are always exceptions, but generally names should be descriptive enough to not need additional explanation.
And context can also come from names of other things, e.g. name of a class / namespace that holds this variable. For example AccessibilitySettings.HighContrast, where AccessibilitySettings holds all options related to accessibility.
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.
Well the author claims that it's not possible for std::unordered_map to get close to other implementations because of constraints that the standard imposes on it. I.e. faster implementations simply behave slightly differently (in ways that are not important to most users).