There's definitely some Unixes that are still trying to do something different, like DragonFly BSD, MINIX 3, Genode and so forth.
Most of it is academic efforts, as always.
Being an hybrid kernel, not like the other UNIXes.
Introducing a super root model, where the traditional root becomes a mere power user.
Being an UNIX where Objective-C and now Swift have the spotlight (with a little space for C++ on IOKit), not C.
Being a hybrid kernel barely has any significance when you don't exploit that fact, which XNU doesn't. Also, it's a hybrid of Mach, which is heavily anachronistic and clunky. DragonFly BSD, on the other hand, actually does through the vkernel mechanism.
I have no idea what you mean by the third one. Are you saying that the root user's privileges are segmented into multiple subsystems? POSIX has had capabilities for that. They suck and they're not actual capability-based security, but they do achieve logical privilege segmentation. Plan 9 and Inferno are the only ones from the Unix-ish lineage who successfully got rid of root entirely.
You can write applications targeting any subsystem provided there are bindings, which there are. For instance, Python and Vala are heavily used in contemporary Unix-like DEs for application programming.
It is not part of any POSIX compliant UNIX.
It also pushes developers into a micro-kernel style of application development, which isn't common in UNIX.
> Also, it's a hybrid of Mach, which is heavily anachronistic and clunky. DragonFly BSD, on the other hand, actually does through the vkernel mechanism.
Besides FreeBSD, I admit I hardly know any other BSD.
> I have no idea what you mean by the third one. Are you saying that the root user's privileges are segmented into multiple subsystems?
In El Capitan, you can only be real root in safe mode. In normal mode there are paths (e.g. /bin, /usr/bin,...) and APIs that aren't available even to processes running as root.
> You can write applications targeting any subsystem provided there are bindings, which there are. For instance, Python and Vala are heavily used in contemporary Unix-like DEs for application programming.
There is a big difference in being a first class language used in the vendor SDK and IDE, and a third party one used by some developers.
Why aren't you hearing about these features? Lots of reasons. Windows is closed-source, so the internal changes you hear about are the ones Microsoft wants you to hear about. Most of the shiny new toys are to support server features that you won't notice unless you're a Windows sysadmin. Most desktop users don't care about internal changes unless they break things, and Windows hasn't broken much on the internal side since Vista. Microsoft's own messaging about major changes has been targeted almost exclusively at Windows server admins.
Edit: That's not even getting into the new app development platform that shipped with 8/10, DirectX 12 adding Mantle-like APIs, first-class support for touch input, hybrid boot, booting from VHDs, etc. Microsoft has been busy over the past few years.
The attempts to follow OS/400 footsteps with a managed userspace in Windows Phone 7.
The OS architecture of Windows Phone 8.
The way they are transitioning Windows into a App Container model with the WinRT execution model.
In terms of installed operating systems and the applications people interact with, Unix or Unix-alike systems win. I don't care if the desktops they use are Windows, or if the phones they run (which have a Unix/Linux kernel usually) don't expose a shell prompt -- the applications they run get the largest part of their functionality through server daemons running on systems running *nix.