Why? All that assumes a home network is setup correctly, which is almost never the case. One huge use case would be all the shitty SOHO routers that don't/can't bridge wired and wireless networks so broadcast and high level discovery/advertising are completely useless between wired and wireless segments. In some cases useless between cells in a mesh, even with 'enterprise' gear this is not as reliable as it should be.

Nintendo made an informed decision and their hardware is welcome on my networks.

> all the shitty SOHO routers that don't/can't bridge wired and wireless networks so broadcast and high level discovery/advertising are completely useless

If you assume basic _routing_ doesn't work, why do you assume a TCP connection from one to another would work? If an AP implements client isolation (as many home models do now for "guest" networks) broadcast would be the only thing that works.

Pretty much every printer you buy now uses Bonjour for printing, so your average SOHO router is going to make sure that works.

I can't fault them, at one point I thought this was the right way to do autodiscovery on a LAN too. Then I learned from my mistakes.

Being pedantic, because there's all sorts of reasons a TCP connection works in the face of buggered routing, not the least of which is that the endpoints are on the same L3 network. Yeah, guest networks are a thing, but a postit note with the WLAN PW is an even bigger thing if most of the home networks I'm familiar with are any indication.

Bottom line is that nothing on an IP network should do something st00pid if it gets a random weird packet from a random IP, because the whole history of IP shows that you will, eventually, get one.

Have you considered what kind of networks a Nintendo device is expecting to interact with?

it probably sends a packet to the broadcast address. I mean "sends a network discovery packet to each device on port" probably is a fucking broadcast.