It's selection bias. There's a huge number of GC language users, but those who experience problems tend to be the ones who comment.

You're right; the vast majority of people use GC just fine and go about their day. We should update little to none when we see evidence of GC hardship.

It depends a lot on the scale of the system, which often means that those fewer users are actually doing things that are more complex and more valuable - either at the lower end or at the high end.

I sometimes run into browser JavaScript GC issues for browser games specifically but on the JVM side i have not run into any pain points for a long time.

(I run a first-person shooter Minecraft server, and for this and other fast-paced gaming in general pause times under a millisecond or so is generally good.)