It’s not ready yet.
The protocol for apps/games to make use of it is not yet finalized.
It’s not ready yet.
The protocol for apps/games to make use of it is not yet finalized.
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.
Please, someone tell comrade Stalin Xi that this is all just a terrible mistake!
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.
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.
Same with Compose even though it’s ironically considered native in the Android dev community.
The easiest way to tell that the app is not native is tooltips (those that appear when you long press on a button in a toolbar). For some reason UI frameworks just can’t agree to display them in the same way, even if they use material design. Compose’s ones are especially bad (some apps like Play store actually have different kinds of tooltips on different screens, meaning they use multiple UI frameworks in the same app).
That can be true for self-contained command line tools, but not for complex programs with actively development dependencies (especially anything dealing with networking or encryption). For example hexchat uses GTK2 which is likely to be removed from mainstream distro repos in the coming years because it has been obsolete for a long time. Also openssl which is known to change its API occasionally which means that anything that uses it needs to be updated to stay compatible.
Wayland is not a drop-in replacement tho. It’s like if glibc developers declared it obsolete and presented a “replacement” that has a completely different API and has 1/100 of glibc functionality and a plugin interface. And then all the dozens of Linux distros have to write all the plugins from scratch to add back missing functionality and do it together in perfect cooperation so that they remain compatible with each other.
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.