[Zetice]

Those things are already true for macs generally, your issues notwithstanding (though you seem to flit between criticizing the hardware and the OS, not sure you even know why your issue is happening), and if you think you wouldn't have these issues with Windows, why use an MBP at all? Surely the mighty Bill Gates will save you from your troubles, yeah?

And not for nothing, but Steve Jobs was a prodigiously arrogant asshole who had very little (if anything at all) to do with the Apple of today, and nearly nothing at all to do with how macOS functions now. The man literally killed himself with his own hubris.

[retrocryptid]

Also... as much as I have asked, Bill Gates doesn't come over to my house to help me edit my registry.

(Though in all fairness, I haven't had to do too much registry surgery since Windows 7)

If you read the thread, you'll discover two things:

1. The MBP is a work laptop given to me by a customer to do development on. I would never pick a Mac to develop Linux code, but that's what my customer has done.

2. I'm not a windows user. Or rather, I have used windows at work, but prefer Linux or BSD systems at home.

Additionally... I can assure you Steve Jobs was a prodigious arrogant asshole who has an awful lot to do with Apple.

[Zetice]

None of this is relevant to the fact that macOS doesn't have a generic "networking intermittently fails to start on boot" issue that you claim exists.

[retrocryptid]

I'm mostly criticizing the OS. When it sounds like I'm criticizing the hardware, I'm probably criticizing the company's inability to ship hardware with an OS that has drivers that work with that hardware (especially considering they control both the hardware and the OS.)

Why do I need to download a kext and monkey with defaults to make the charger work? This was the kind of thing Macs were supposed to free me from.

[Zetice]

You don't, is the point. The fact that you have to do those things (and not a meaningful number of others) make it clear it's a you issue, not a macOS issue.