A lot of these questions are answered here: https://ravynos.com/faq

To summarize...

There is a WINE-analogous project, called Darling: https://www.darlinghq.org/

The goal for ravynOS is to be analogous to ReactOS. Much like ReactOS and WINE, ravynOS and Darling share a lot of Cocoa code.

For the problem of OpenStep implementations specifically, a bespoke software stack has the benefit of being able to put Mach messaging into the kernel, where it is much more performant.

They chose the FreeBSD kernel over Darwin for the sake of hardware compatibility (though of course NeXT Mach is one of the most widely-ported kernels of all time...)

There is also overlap with GNUstep, helloSystem, and other projects in the broader "open-source Mac/NeXT" space, though ravynOS (obviously) prefers BSD/MIT/Apache-style licensing over GNU-style licensing. Nevertheless, ravynOS currently uses the GNUstep libobjc2 runtime, a bit like how most of the Unix world used to depend on gcc.

▲

9dev 5 hours ago | parent | next [-]

> There is a WINE-analogous project, called Darling: https://www.darlinghq.org/

Missed opportunity to call it Cider.

	▲	mlyle 4 hours ago \| parent [-]
		There's already been a Cider; it used some Wine code to ease porting games to MacOS.

▲

mistrial9 an hour ago | parent | prev [-]

> of course NeXT Mach is one of the most widely-ported kernels of all time...

actually the broader Mach kernel, not specifically the NeXT variant, is the one with a documented history of extensive portability