No one is making any money getting Linux sleep to work on a Macbook Pro 2015. That is why it doesn't work. Sleep can work on Linux, but it is hardware/driver specific. That is why you should only buy hardware where there vendor invests in proper support.

Either the vendor needs to invest in support, or you need the community to come together and build support like with Allwinner chips (which are dirt cheap, hence people building mainline, blobless support). Apple doesn't invest in Linux kernel support, and their userbase isn't motivated to do so either :/

As if.

My Asus Linux supported netbook wasn't properly a flawless experience and those beautiful AMD open source drivers mean I will never get back the same OpenGL feature level and hardware acceleration provided by fxgl, that I had at sale time.

I too attempted to get Linux working on a modern MacBook. It's terrible. The keyboard and touchpad aren't connected to the USB bus (like on any other sane laptop out there), but instead to the SPI bus. ACPI is terribly broken (it always has been, but not quite this bad) and with the newer Macs with T2 chips, there's a chance you won't even be able to access the nvme drives from Linux at all.

I wrote a post about my experiences here. I got almost everything working except Wi-Fi or ACPI/suspend. It wasn't easy and I would not recommend Apple's non-standard hardware.

https://penguindreams.org/blog/linux-on-a-macbook-pro-14-3/

If memory serves the SPI bus thing is down to the UEFI - that is, when you boot into Windows, for example, it uses it via the USB bus. I can't remember the reasoning for this.

I battled this for months and no workaround worked. It sadly forced me back to macOS. I'd reopen the lid later and find the battery drained and lose work if I hadn't saved before closing the lid.

Stepping back a few feet to get a bit of perspective, it does seem like the OP is using the most common developer machine in history. Devs are historically Mac people, and are afraid of newer ones, so they hoard the 2015 MBP.

It would seem that if a developer OS was going to work correctly on any machine, ever, that would be the one, since an issue there would bug the largest possible group of people who were capable of doing something about it.

But it doesn’t. I think he has a valid point.

> Devs are historically Mac people

No, this is simply untrue. Once you step outside of the US SV and WebDev bubble, there are millions of developers writing code for on Windows and Linux for stuff that you never even heard of. Mostly because it's unsupported on Mac due to the locked down ecosystem. Obscure machine controllers and their drivers, planning software, banking software, regulatory mandated software for certifications, etc.

It is really funny, since it wasn't too long ago since I met the first mac-developer. I wondered quite a bit about that.

I did industrial cs, so development was mostly focused on embedded devices and nobody here used a mac for anything.

Wouldn't have worked anyway, since people tend to be tinkerers. That is usually not a group using locked down environments.

My statements still stand. The fact that there are many users of the hardware simply means that there might be many potential funders of a feature like this, or that it is more likely for someone to fix the problem for free in the near future.

Indeed. But it does tend to lend more credence to the point of the person you responded to, which is "nobody is ever going to make Linux work on a computer".

You're certainly correct that that's due to a combination of nobody caring enough to pay for that to happen (and the few people who could in fact do something about it simply configuring their own personal machine to work correctly.)