Hacker News Reader

Comment by minerva23 | Hacker News Reader

> why the heck doesn't the macOS kernel support native containerization?

Because Apple has no plans of growing their server OS marketshare. I know there are benefits of using namespaces (containers) in the desktop market, but they don't sell iMacs/MBPs. Exterior design and heavy marketing is their sales strategy.

View on HN

I never understood this, because surely some huge percentage of developers use Macs. Enterprises buy stacks of them nonstop. Just making that group happy would get you the reputation of being a developers machine, for serious computer people, which could translate into laymen purchases too.

Would developers really be happy with containers running macOS inside? Production is running Linux, so they need two sets of images and their local image will be different from the one running in production.

I'm really not sure what comment you're replying to but Mac developers write code that runs on linux primarily using Docker and "VMs" that run linux on docker. Like; probably 75% of the devs on the west coast do this.

Mac developers run code that runs on iOS, iPadOS, watchOS and macOS, that is why they are Mac developers.

Otherwise they are just UNIX developers that don't care which POSIX platform they are actually using.

Yeah, I meant developers who prefer to use macs.

iOS, iPadOS, watchOS and macOS applications aren't made out of thin air, they also need developers.

Also creating their own SoC that outperforms others in the space.

"Exterior design and heavy marketing is their sales strategy" this is old, boring and not even true.

containerization won't just help in the server-space. It has use-cases in app development like CI.

Apple would like you to move to XCode Cloud[0] in the future, running CI pipelines on your local device is soooo last-century.

[0] https://developer.apple.com/xcode-cloud/

Reply on news.ycombinator.com