A lot of online gamers are gaming competitively! They're playing Fortnite et al. And the vast majority of folk, myself included, don't have the background in networking to use anything other than rule-of-thumb advice.
The thing with networking, is that the rule of thumb advice (cable > wireless) carries so many caveats that it's worthless because it is complicated and does depend on so many factors. You might as well ask is linux better than Windows because you'll get the same type of meaningless advice/opinon. ¯\_(ツ)_/¯
Here JPT's point is that Wifi is inherently unstable versus cabling, even if you aren't seeing that instability because the network is dealing with it for you, and so it's a good idea wherever possibly to cable up.
If you're using the term "unstable" to imply that packet loss doesn't happen on ethernet then you'd be wrong, because it happens a lot and just like wifi, the router will re-request missing packets from the device if it doesn't arrive in a timely fashion. Where wifi has gotten smarter than ethernet is predictive retransmission, which is where the device pair adapt to changing to wireless conditions and the sending device begins to send more redundant packets to keep latency low - because the latency spike is the (send) (wait) (fail) (re-request) (re-send) (receive) event chain. WiFI QoS has iterated massively in the last decade because it's had to.
Humans have been transmitting information wirelessly a lot longer than they have been trying to send data over copper or fibre optic cables.
Anyone with advanced knowledge and hardware to create their own wifi solution that's comparable to cabling is of course exempt from such advice, just as any car mechanic doesn't need to read "10 tips to prepare your car for Winter" from a Compare the Market newsletter.
And people with no knowledge will create a poor wired network because they they believe wire > wireless, and that's my point. Oh cables are better? Well I don't have an ethernet connector but I can buy this USB ethernet adapters. Sure you can, but the USB-ethernet over-protocol is ~10ms for just plugging it in.
JPT was talking about pings of 10-100ms between device and the local router and I don't even know what kind of equipment or environment would result in such a poor performance, maybe during an EMP burst? Or if your router has no antenna? Or is twenty years old? My router is an
ASUS DSL-AC68U which I bought in 2015. This isn't even a WiFi6 device, this is an old 802.11ac model and my pings via a bridge (because the router is a good way away) are:
Pinging away.. said:
dsoup@MacBook-Air ~ % ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=8.434 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=4.443 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=5.197 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=5.711 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=4.077 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=5.367 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=4.565 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=1.861 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=3.616 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=5.439 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=4.235 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=5.406 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=2.381 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=2.491 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=2.928 ms
64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=7.180 ms
Modern WiFi6 routers can be
a lot better. WiFi7 will be better still. But the router is critical in any network. Using a cheap router is where people go wrong, the ASUS was not cheap in 2015, and ASUS still keeps deploying firmware updates for it! A cheap wifi router is definitely worse than a cheap ethernet router.