I’m well aware how short 100ms really is and it is very obvious if your inputs are off by 100ms or more; rhythm games are rarely that strict, but I’ve also played games where some inputs had to be timed to within 1/60th of a second (~16.7ms)
But the results… calling something “bad” for 3ms of latency is a bit ridiculous. That’s only significant to a cat, to us larger meat sacks 100ms would be blazing fast reaction speed, making 3ms negligible. For an average person it means even less.
You are conflating reaction time and response time. They are very different things.
Yes, your reaction time is in the 100s of miliseconds, but it doesn’t take much of a delay in the response to your reaction before it becomes perceivable, and the response time is what was measured here.
If you have ever played rhythm games, then you may be aware that some of them have settings that allow you to offset the delay, such that your pressing a button at the exact same time as the note plays is also registered as happening at that time, even though it took some additional time for the input to reach the game. Without such a setting, you intentionally have to press buttons early (how much depends on your setup) to ensure that your input registers at the right time. A delay of 100ms would be extremely obvious
Let me remind you that you wrote that,
People complain at something not working are missing the point.
It’s open source. You spot something you don’t like, change it.
Learn to code, contribute, fix things.
There is very little stopping you.
Do you think that you can fix something not working by writing documentation? Or do you think that you can fix something not working by testing? Or do you think that you can fix something not working by investing in visual elements? And so on and so forth.
No. Obviously not. If you want to fix something not working, then you have to get your hands dirty with the source code
Time investment is a barrier to entry.
I say this as somebody who has already made the time investment required to learn how to program, and as somebody who keeps investing time to maintain and to improve their skills in that area. Expecting the average Linux user to do the same is ridiculous.
Have you made that investment?
Yes. Firstly because no distro has everything in their respositores, and secondly because different package managers serve different purposes.
The closest to an all-encompassing package manager is perhaps Arch with AUR, though you are forced to use tools beyond pacman if you want actual package management for the AUR packages. AUR has also shown itself to be a massive liability, since the only way the project has been able to cover as much software as it does, is by doing next to no vetting of the submitted packages. With predictable results
The GUI that came with my distro only covers 2 of the 4 package managers I mentioned. And I’d have to use a GUI
If the subset of software available in the Debian package repository includes all the software you ever need, or if you are OK with potentially waiting years to have missing software added, and if you are OK with what are likely outdated versions of that software, then yes, all you need is apt-get install.
But, personally, I don’t think I’ve had a Linux install that didn’t include software installed from other sources
I somehow forgot you had to download every program yourself and update it yourself or put up with a third party update app at all times. I’ve only been away from Windows for like a year but it’s like “I completely forgot about that”.
The author exaggerates how bad it is, to be honest. The built in winget package manager solved most of my needs for installing and updating software while I was still using Windows, and what it left is no worse than the situation on Linux. There are also alternatives to winget, like Chocolatey.
In some ways the situation is actually worse on Linux, since I regularly use 4 different package managers on Linux: apt, flatpak, pixi/conda, and uv/pip, on top of having to manually download and install software, some of which I have to compile myself
There is very little stopping you.
You mean besides the huge time investment required to get to the point where you can meaningfully contribute?
Because X11 is mostly dead and the guy who’s is trying to keep it alive has a questionable understanding of the programming language it is written in, to the point where he got ejected from the original X11 project for constantly and pointlessly breaking stuff. See also https://github.com/X11Libre/xserver/pull/56
That is simply not true. See here for a list of behavior that is considered undefined in Rust: https://doc.rust-lang.org/reference/behavior-considered-undefined.html
However, most (all?) of these require the use of
unsafe, which helps narrow down where the problem might be, if you trigger any of this behavior