Call me odd, but I like native software — web-apps et al are not my style. Similarly, bastardising everything so Linux binaries run on it kind of defeats the point (at least in my mind). But yeah, I'm odd.
> bastardising everything so Linux binaries run on it kind of defeats the point
Is there all that much of a difference between the kind of "secondary syscall ABI" approaches that allow OSes like Windows and Illumos to virtualize Linux binaries, and autoconf-based porting of those projects so they compile for the target OS, if they only use POSIX facilities that both OSes offer the same way anyway?
I mean, I agree with you when it comes to e.g. programs that use heavy amounts of OS-specific concurrency or IPC primitives. Postgres in WSL on Windows does not have the same concurrency semantics as MSSQL on Windows does, because Postgres is using POSIX concurrency primitives and MSSQL is using NT concurrency primitives.
But if there's a subset of your kernel's syscall ABI, that already has those same semantics, and really can just be 1:1 mapped with maybe a few extra instructions to handle different argument passing conventions—then does porting such a program to the OS really achieve anything?
