No, this is perverse in the worst way possible.

It's incompatible with modern debuggers.

It's incompatible with shared libraries.

It's limited to a feature-poor "unified" API (that might as well be seen as a crippled VM).

It's complex in both interface and implementation. The bad aspects of Unix made even worse.

The justifications make no sense whatsoever. It wants to do future-proofing but invents an adhoc "VM" with hardcoded OS interfaces that are meant to be treated as private. For macOS, I doubt binaries will work in the next release or two, nevermind 10 years.

It's a fun toy or troll, but if you're looking at this for serious work I suggest you steer well clear.

> It's incompatible with modern debuggers.

Any debugger that can't debug this binary is broken and should be treated as such.

That's true, but I think they meant that it fails to actively support debugging the way a not-broken-by-design modern executable file format should.