It still i behind that pretty GUI....Go and have a look. Alll BSD userland under there. running on top of a Mach/BSD hybrid kernel.
The underlying operating system is called Darwin, it has 4.4BSD heritage inherited via NeXTSTEP and it had a BSD userland based on FreeBSD 4.
The former is the Mach part and the latter is the BSD part.
4.4BSD is a late version of one of two original UNIX flavours - SysV vs Berkeley. It includes original UNIX source code. FreeBSD was born out of the cleanup project that aimed to replace all AT&T proprietary code from Berkeley flavour namely 386BSD.
In OSX, kernel part used to be POSIX/UNIX because they had aligned syscalls and other stuff already. For the userspace POSIX APIs FreeBSD imports were slightly changed and that's it.
This all happened about 15-20 years ago.
As far as I know, Apple has not send further versions for certification and it doesn't have POSIX.1-2017 compliance.
There is a test suite so you can run it if you have a modern mac, I don't. I strongly suspect it will fail.
Apple own the UNIX actually trademark
No they don't, Open Group owns it. Unix wars of early 90s are a good topic to read into to grasp all the historicity behind a very complicated story with a lot of stakeholders. Apple was not among them, they're or were just a licensee like QNX used to be.
My recollection is that the BSD was known in the early days as "Berkeley UNIX", as it's based on the UNIX V6 originally, mostly by way of added programs, not replacements. When we ran 4.1BSD, the man pages were definitely those of AT&T UNIX. An organization back then could get a 9 track tape(s) from AT&T for a very modest fee. This was before the 1982 AT&T breakup.
en.wikipedia.org
BSD and Berkeley UNIX share a common lineage, but due to code rewrite above, it's not a direct descendant like in Darwin->BSD case.
Linux is a rewrite of (mostly SysV) UNIX as far as external API is concerned, 386BSD is a rewrite of Berkeley UNIX as far as internal APIs are concerned.
The aforementioned OSX contains code from both.
At my company we had a few anti-Linux/Pro-Mac/BSD-Zealot guys that tried to get IT to buy some (the G5 model) for, I dunno, some reason they’d try to justify later, but they thankfully failed. (These were the same folks that eventually did succeed in getting us to waste $15,000 on a pair of absolute boat-anchor UltraSparc III servers to run the same two-factor auth software that we could have just run on RedHat using the same Xeon servers we had literally hundreds of available.)
Some people just *really* get the idea stuck in their heads that the same bits smell sweeter if they plop out the back of whatever their favorite less mainstream platform is. These days I generally just sigh and imagine these people also *insist* that records sound better than CDs because they can “hear the music breaking up” at 44.1khz and think something similar happens if your CPU has too ugly an instruction set or whatever.
There is a ton of pros and cons in practical scenario most of them business related.
FreeBSD is a far more stable OS than Linux in every aspect for server performance. However if hardware support is not there and you don't have enough people with skills to implement it the project will fail.
One of the red flags immediately raised about your team is that they've approached software choice as #1 requirement without looking at a TCA/TCO of the complete system.
The other red flag is conflating Mac experience with FreeBSD. It's same and totally opposite. Same is clear venue how to do something, ton of quality documentation, everyting important is already on the base system, etc. The opposite part is that Mac is a few-click experience and FreeBSD tends to be manual configs all the way.
Today even Linux people underestimate the level of automation in their "non-noob" distribution such as Debian. "That's it, I hate systemd, moving to FreeBSD", then tries to get his desktop up and running for weeks because you need to learn a metric ton of new stuff. I have graduated on FreeBSD kernel programming and been inside the FreeBSD community for 20 years, for me it's easy to get a flashy modern desktop running, because I'm aware of 20-30 commands that haven't changed for ages. Someone that thinks it's going to go smoothly without real experience is terribly wrong.