[smoldesu]

Coming from Mojave, I was really disappointed by the Playmobil design philosophy and limitations on executable linking. Also something must have changed internally, because post-Big-Sur Nix installers have the most ass-backwards way of working around APFS. Making a comfortable dev environment on MacOS leaves my machine feeling like it's bursting at the seams...

I'm sure it's a great tool for creatives who want to loathe Windows with the rest of us, but for development MacOS has become more of a hindrance than a help. Even WSL2 feels nicer to use than baremetal Darwin deployment.

[dagmx]

What limitations with executable linking have you found? I couldn’t find anything specific and didn’t run into any issues myself.

[smoldesu]

All my 32-bit plugins broke in Ableton Live, and Proton stopped working when I tried Catalina. Without my music toolkit, games or preferred programming environment, MacOS doesn't really have much left for me these days.

[dagmx]

That’s not really an executable linking issue. That’s the OS dropping support for 32-bit code in general from Catalina onwards.

[kitsunesoba]

And it was no doubt done to ease the transition to ARM… it means no need to implement 32-bit support in Rosetta.

[cwzwarich]

Rosetta does support executing 32-but code in alternate code segments created in a 64-bit process, used by CodeWeavers’ Crossover: https://www.codeweavers.com/blog/jwhite/2020/11/18/okay-im-o...

[dagmx]

This post here has a section on the reasons to drop 32-bit

https://pilky.me/apples-technology-transitions/

But essentially storage and memory savings, maintainability savings and some issues with the ObjC runtime.

I assume part of the issue too is being able to enable pointer authentication, which afaik uses the higher end bits to store data, and being able to do that allows them to secure the OS better. So 32-bit support likely was a security risk factor as a result too.