Classic GitHub issue thread: Someone shows up and tries to explain it’s not a bug and never could have worked. Everyone else points out that it does work on other Mac hardware. Person doubles down and tries to claim that the bug was that it ever worked, and not working is the correct behavior. New Mac OS beta release fixes the bug and makes it work. Nothing related to the repo was changed.
This is actually what’s interesting
remember how there used to be people whose lifestyle was answering Stack Overflow questions? 3 years from now we're going to be looking at charts showing engagement from GitHub Lifestyle people going straight down too.
I couldn't get bridged networking to work with my M5 machine and VMs running on Parallels. This thread here would seem to indicate it's a known issue (with no updates or resolution :/ ) - <a href="https://forum.parallels.com/threads/m5-macbook-air-windows-11-arm-coherence-wont-work-nor-bridged-networking.369660/page-2" rel="nofollow">https://forum.parallels.com/threads/m5-macbook-air-windows-1...</a>
The M5 Pro and M5 Max support Wi-Fi 7 and Bluetooth 6 via Apple's N1 wireless networking chip, while the base M5 supports Wi-Fi 6E and Bluetooth 5.3.<p><a href="https://en.wikipedia.org/wiki/Apple_M5" rel="nofollow">https://en.wikipedia.org/wiki/Apple_M5</a>
Don't try to do professional work on consumer hardware.
That's super weird.
Remember, if shoes were like software, they would explode while you're trying to tie the laces, because the first of the month landed on a Tuesday.
Unfortunately most consumers put up with it, instead of handling it like shoes, returning them to the shop for a refund, or if surviving the explosion, a lawsuit.
Analogy kind of falls apart when you consumers are willing to put up with quite a lot to save a buck. They happily build their own furniture for example.
Shoes today are garbage that wears through within half a year; consumers are accepting it and coming back for more.