I understand the need for it to be in Siemens NX, but do they really run it in Windows VMs? As far as I know NX isn't certified to run in VMs without Nvidia GPU passthrough (aka Macs). It seems more sensible to maintain a fleet of Windows desktops specifically for CAD and industrial control.
So this is all pure speculation, but seeing as they are a hardware company I wonder if they have some sort of internal only server chassis to house apple motherboards for their backend, tolerate asahi linux for this? No real external market for apple servers so they don't develop it past "Ok for internal use"
The more I think about it the more I doubt it, even if you make your own hardware it is hard to compete with a commodity server, but it is an interesting thought.
Update: or perhaps they do, a sibling comment had a picture of such.
Only if the marketplace makes sense. They can't just roll their own CAD system to use internally - mostly because it's a huge space and it requires working with external stakeholders/vendors
This is the typical thinking of the toolmaker. It is not useful in markets. Apple is not in the business of engineering software, their in the business of consumer hardware.
NX supported macos and Linux until 2019. The situation is kinda sad/ironic considering that many big CAD packages have their roots in classic UNIX workstations, and afaik that was one of the major usecases for RedHat desktop. With the general decline of MS and Windows I imagine CAD companies must be reconsidering their platform choices. But of course big ships turn slowly so who knows when anything concrete might happen
Professional 3D CAD software is pretty much Windows only. Especially with a company like Apple where you have complex models with many designers working on it you aren't going to risk using anything other than the likes of NX, Catia, Creo, or SolidWorks (though I shudder at how frustrating SolidWorks would be in that use case).
Why is it a cluster fuck? When it's been virtually unchanged and stable for the past 30 or so years, which is how Winamp 2.95 can run on WIndows 11 today and how Wine can so easily run Windows games. Way better than Linux and Mac have historically provided for compatibility.
I still think that it’s one of the great ironies of our time.
Linux itself bends over backwards to avoid breaking userland, to the point where there is a substantial amount of cruft when interacting directly with the kernel.
Only for GNU to say “fuck that” and create a widely mockable situation, one of the worst targets of modern programs for stability… to the point where people start using alternative libc’s specifically to statically link them.
Not all parts of Win32 were designed equally well. File IO, process management and most of the threading primitivs have aged really well. Thread management hasn't. The GUI parts are a sometimes hacky mess because behavioral changes created mismatches between what functions were specified to do and what that gets actually translated to. Permissions are a pain in the butt with complex ACLs, transparent file access redirects and how process elevation works.
I guess not for this use case. There are many industrial use cases for which there are no macOS versions. In fact, Siemens NX was once available on macOS AFAIK, but isn't anymore.
I wish overhead (cut away to passenger layout) and side scale drawings of all cars existed. That way you could directly compare the vehicles. You'd think such information would be needed (in the U.S.) by the NTSB; and, thus, be freely available.
Same, I recently upgraded to a similar car but slightly different segment, same brand. I couldn't find any data about it, I asked llms and they all told me given the available data the cabin size should be basically the same in term of passenger comfort. Completely wrong, there is much more space for both front and back passengers
Electronics has this, more or less. Every device with a radio needs FCC certification, and the filings are public: internal photos (PCB shots good enough to read chip markings), external photos, test reports, manuals. Look up the FCC ID from the device label.
Seems like this URL has only been live (at least first archived [0]) around May 2026, originally with only 13 products. Great to see them add more since then, now close to 90.
Oh my word, have a look at the Apple Watch Ultra 3 and the level of detail.
Now imagine you’re the manufacturer and this is the spec you have to meet. Of course, they will have tolerances but still this is incredible. I wonder what the accepted rejection rate is?
I'm also curious how Apple handles surface roughness? The dimensions only give you part of the picture.
In my opinion it only makes sense for reflective surfaces (e.g. cars) to have nicely flowing reflections, while most of Apple's products have a matte finish. In 2D UI elements it most definitely makes no sense. But some designer must have been a big fan of this and somehow they now use it everywhere.
I always imagined shops in China got out the calipers and made measurements from scratch every time a new iPhone was released. Never knew Apple made it this easy to manufacture Minion iPhone cases
That’s obviously the people who are really using it, but I assumed you had to pay Apple to get it.
So either you made your own measurements or if you were doing Made For iPhone and they would give it to you as part of that program which surely you must have to pay for.
I assume there's NDAs in place with some vendors pre-release, since my understanding is some accessory vendors get the needed info before new models are released, so they can spin up their lines and have accessories ready to go when the new model hits the market.
(but I could be wrong; NDAs w/China? no idea what the time between announced/released/shipped is typically; I last bought Apple product in 2009...)
It's nice but lots of companies do this if their equipment is meant to be used with other equipment from third parties. Frankly I'm surprised they only provide it in 2D PDFs.
This kind of thing was available (although more difficult to find) well before the EU started on their Apple quest - e.g. I had the dimensional drawings for whatever phone I had in late 2015 (6 or 6S, I forget) because I was making graphical inserts for my clear case using my Cricut with dimensions from the Apple PDF.
No decent engineering firm is going to want to work with FBX or Blender files. In fact they probably wouldn't even know what to do with them. Even proper model formats such as STEP files don't give you the details that are on a drawing that you actually need to do anything useful with these.
I’ve only dabbled with cad for 3d modelling in Onshape. It seems that there all kinds of ways to add measurements in the render files. Not sure about blender.
MBD is a thing, however that doesn't really matter here, for making accessories you can more or less just assume all dimensions are perfect since you need some compliance for the accessory to be installable. What I'm talking about that can't be encoded in a model easily are things like the keepout area for the camera.
The reason you don't want Blender files at all in any sort of engineering is because it's a mesh. You can't pull any useful information, even something simple like a radius, from a mesh.
I'd love to see a full fleet of Mac servers (XServe was a handsome piece of kit), but I believe one shall choose their battles.
The more I think about it the more I doubt it, even if you make your own hardware it is hard to compete with a commodity server, but it is an interesting thought.
Update: or perhaps they do, a sibling comment had a picture of such.
Not sure about the backplane architecture. I’m pretty sure they are custom datacenter rack units.
Very hard for Apple, or Linux to do much about that - especially when Nvidia considered it's drivers key IP.
Couple that with a relatively small market - and it's hard to justify supporting multiple platforms.
MacOS versions are more commonly found in the low end of the market, e.g. Fusion 360.
Linux itself bends over backwards to avoid breaking userland, to the point where there is a substantial amount of cruft when interacting directly with the kernel.
Only for GNU to say “fuck that” and create a widely mockable situation, one of the worst targets of modern programs for stability… to the point where people start using alternative libc’s specifically to statically link them.
What a monumental failure.
There are some open source options but those aren’t taught at school afaik.
https://apps.fcc.gov/oetcf/eas/reports/GenericSearch.cfm
or
https://fccid.io
for a better frontend.
Nobody set out to build a teardown archive, it just falls out of the certification process. I wish cars had the equivalent.
0: https://web.archive.org/web/20260512182718/https://developer...
Now imagine you’re the manufacturer and this is the spec you have to meet. Of course, they will have tolerances but still this is incredible. I wonder what the accepted rejection rate is?
I'm also curious how Apple handles surface roughness? The dimensions only give you part of the picture.
https://arun.is/blog/apple-rounded-corners/
In my opinion it only makes sense for reflective surfaces (e.g. cars) to have nicely flowing reflections, while most of Apple's products have a matte finish. In 2D UI elements it most definitely makes no sense. But some designer must have been a big fan of this and somehow they now use it everywhere.
The openness is easily worth it.
As others have mentioned, these are more useful for when they don't, i.e. before the actual release.
So either you made your own measurements or if you were doing Made For iPhone and they would give it to you as part of that program which surely you must have to pay for.
(but I could be wrong; NDAs w/China? no idea what the time between announced/released/shipped is typically; I last bought Apple product in 2009...)
You might want to pay for the Made For iPhone certification for some things, but I doubt most cases have it.
https://developer.apple.com/accessories/Accessory-Design-Gui...
... and nothing else.
I guess other MBs and MBPs are top secret.
Edit: close, but not quite
I mean these seem nice for print-decorations...
The reason you don't want Blender files at all in any sort of engineering is because it's a mesh. You can't pull any useful information, even something simple like a radius, from a mesh.