It is super easy, pick any random UNIX tutorials and follow it using Visual Studio, or Windows Terminal.

But certainly, but I invite you to pick any of this supposed Unix tutorial and try it on AIX or HP-UX the other two certified Unix and see if it works.

As a reminder, AIX ships with ksh, the IBM XL compiler, is configured via smit, stores parameters in ODB. It has no port system and while it supports gcc, the gnu linker doesn’t work. Also it is entirely compiled for the Power ISA architecture.

▲

pjmlp 2 days ago | parent [-]

I have experience across Xenix, DG/UX, Solaris, Aix, HP-UX, Tru64, NeXTSTEP, OS X, FreeBSD and all major Linux distributions starting with Slackware 2.0.

So I might know a thing or two about portable UNIX code, and getting it to run on a non-UNIX system like Windows.

Here is a reminder for you as well, one of those follows the same dynamic linking model as Windows.

▲

StopDisinfo910 2 days ago | parent [-]

You have experience with them and you are trying to pretend a guide written for them will work on MacOS. I’m glade to know you are not misinformed but actively disingenuous.

I stand by my point. Unix semantics don’t really exist in a meaningful manner. The SUS gives you very little.

To get back to the Windows side discussion, you can get a POSIX compliant shell on Windows in minutes nowadays be it Cygwin, gsh, git shell or WSL if you don’t mind using virtualisation and the C headers defined in the XBD are also minutes away. The days when developing on Windows was painful are long gone.

The rational for MacOS at this point for me is pretty much limited to “I want a MacBook as a status symbol”, same than the iPhone. They are nice machines. They are just far too expensive for what they do imho at least in Europe where Apple prices them significantly higher than in the US.

	▲	pjmlp 2 days ago \| parent [-]
		Try to call fork() on Windows.