Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Well x86 at one point, arm both the 32 and 64 bit versions. I think they had RISCV support in their source tree at one point but not really at a commercial level. It does cover a lot different levels of hardware though
 help



Does Apple use macOS in servers in its datacentres? Or are they all Linux?

Surely at a minimum they need macOS for CI.

Apple does have one advantage here-they can legally grant themselves permission to run macOS internally on non-Apple hardware, and I don’t believe doing so legally obliges them to extend the same allowance to their customers.

But that might give them a reason to keep x86_64 alive for internal use, since that platform (still) gives you more options for server-class hardware than ARM does


They do run Apple Silicon in data centers, so perhaps another custom version of Darwin + their system frameworks. It is hard to tell without some leaks :)

For Private Cloud Compute: “a new operating system: a hardened subset of the foundations of iOS and macOS tailored to support Large Language Model (LLM) inference workloads while presenting an extremely narrow attack surface.” https://security.apple.com/blog/private-cloud-compute/

I wonder if there is any chance we might see another Xserve?

If they’ve got Apple Silicon servers in their own data centres…


They use Ubuntu on x86-64 servers, at least for iCloud. Backends for iCloud, Photos and Backups etc. are written in Java.

Any sources or more information on that?


For the Java bit at least, this aligns with job descriptions I’ve seen and recruiter outreach I’ve received (long time ago though, maybe 5 years).

NeXT added a Java variant to WebObjects and it was for several years the main server side infrastructure, after being acquired by Apple.

Nowadays you can usually still find Java and JVM languages like Clojure (Apple Maps), on Apple's job ads.

How much of it is still Java based, no idea.

I imagine XCode Cloud has nothing to with it for example.


Unfortunately I am the source in this case. It is from having worked on them personally. :)

PPC32/64 of course, and for a long time Darwin still contained remnants of its predecessor's support for SPARC, PA-RISC, and m68k.

Which Apple products run arm32 XNU? Their first Apple Silicon CPUs were already arm64.

Well there were still the historical arm32 chips in their iOS devices, but until recently the watches were a cursed arm64_32 (or something like that) which is arm64 with 32 bit pointers iirc.

I should have just soureced this, They had PowerPC not RISCV in there source tree that was the X factor one. The Arm32 bit variant is closed sourced (leaked before) but was supported until IOS 11. XNU is really old almost 30 years! And before XNU there was the MACH kernel and the larger BSD tree it was built on which is an argument that it probably had a initial MIPs release too but I couldn't source the truth on that.

[1] https://en.wikipedia.org/wiki/XNU


Is mc68k or PPC still in there anywhere?

I'm sure there's vestiges of them somewhere, but the underlying support (the architecture specific parts of the mach portion of the kernel) is gone for those archs.

I wouldn't be surprised if they keep a minimal Power base maintained behind closed doors. It's how they managed to jump ship to intel so quickly, they never stopped maintaining NeXTSTEPs x86 port

I seriously doubt it.

Apple's ARM implementation is in a really good place right now. It would take something extremely compelling to get them to consider any other architecture for an application processor, especially considering that it'd mean giving up some degree of control.

Power is probably not where Apple would choose to go unless something really unusual happened. It's essentially just IBM's pet architecture at this point.


When I mean minimal arm base, I basically mean making sure XNU at least compiles on PPC64. I don't doubt they'd likely never have a use for it, but they maintained intel support behind closed doors when macos forked from NeXTstep and nobody thought they'd need that

I would honestly be shocked if they were.

They've been making quite a few changes to the virtual memory code over the past decade, and keeping those vestigial arch's around is a pretty big maintenance burden. It'd probably be less work to just add the arch as if it were new when it's needed at this point since the kernel itself is pretty portable.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: