I'd say this resource is more aimed at the developers writing the stuff on the other side of the APIs a typical desktop application calls.
Not that I'm in favour of developing desktop applications in JavaScript or anything. I don't really think those are a great idea. It's just that there's a lot of intermediate steps between "let's use JavaScript" and "let's worry about using the best x86 opcodes" which are perhaps more sensible than either extreme.
The software people enjoy using is typically written in C++, Rust, or Swift.
Nobody writes desktop software in a GC'd language that doesn't suffer from noticeable performance issues. There's a reason why people bitch about e.g., Microsoft Teams, and it has a lot to do with language choice.
Garbage collected languages are fine for the desktop, there's plenty of software written in C# or Java that performs perfectly fine. It's mostly the web stack that tends to be bloated and slow.
Name me a C# or Java desktop program that doesn't have annoying GC pauses or stutters. Name me a C# or Java desktop program that isn't bloated and slow compared to the equivalent C++ program.
Programmers choose GC languages because it's what they want, not what users want.
Not that I'm in favour of developing desktop applications in JavaScript or anything. I don't really think those are a great idea. It's just that there's a lot of intermediate steps between "let's use JavaScript" and "let's worry about using the best x86 opcodes" which are perhaps more sensible than either extreme.