We’ve gone way off topic…but it’s my thread so whatever 🤣

Here is some potted history of the windows networking stack:
https://tangentsoft.net/wskfaq/articles/history.html

If you want to hear the real forefathers of PC networking they are here at the history section of the Ethernet Alliance:
https://ethernetalliance.org/voices-of-ethernet/

Now back to 2022 and MacOS maybe 🤔 🤣?

In reply to a post by Pheasant:

Now back to 2022 and MacOS maybe 🤔 🤣?

But but.... Bob Metcalfe!

In reply to a post by jchamier:

My understanding is the NT 3.1/3.5/3.51/4/win2000/XP stack was built on BSD design. I also read that with Win7 and later the TCP/IP stack was rewritten in house by MS to perform faster.

Yes. Next Generation TCP/IP stack

The BSD design wasn't that great, susceptable to "ping of doom" and other exploits that would blue screen a box over the wire. (As OS X/macOS and plenty of Unixes also would crash, including SunOS/Solaris, HP/UX, and others). Of course BSD and others worked on theirs in the early 2000s as well, so the only constant is change.

The musings of Terry Lambert about his time at Apple and work done under the cover of MacOS make for interesting and amusing reading

Most of my Unix/Linux colleagues dislike macOS as the built in userland (command line) tools from Apple are quite old. They tend to use package managers such as brew to install non-apple open source (GNU) type utililties, or on Intel Mac's run a Linux VM. (harder on M1/M2 as the hypervisor support is limited, and less compatible distributions, but this is improving slowly).

Well yeah brew is excellent.

Apple Silicon runs Windows 11 (for ARM), Ubuntu 22.04 desktop (had to graft that one together) and server really well under virtualisation. Just give the box enough memory but grunt isn’t really a question. You wouldn’t know it was virtualised.

In reply to a post by jchamier:

In reply to a post by Pheasant:

Now back to 2022 and MacOS maybe 🤔 🤣?

But but.... Bob Metcalfe!

Hehe. 😎 They’re all legends (for us long in the tooth EE/computing/networking nerds anyway).

In reply to a post by Pheasant:

Apple Silicon runs Windows 11 (for ARM), Ubuntu 22.04 desktop (had to graft that one together) and server really well under virtualisation. Just give the box enough memory but grunt isn’t really a question. You wouldn’t know it was virtualised.

The problems we have are commercial, MS won't actually licence ARM windows, but they seem to turn a blind eye to home users. So as an insanely large corporate (which makes money from MS consulting) our lawyers won't let us go near it. Its causing upset in our Apple fans as many ran Windows VMs for monthly/weekly use, and now they need two laptops. We blame Legal

Yeah I'm my own legal team. So my in-house general counsel had pause for thought, then gave me the nod. 🙈😂

All TCP/IP networking nowadays is built on the Berkley Socket interface, which originated in BSD 4.2. Different vendors will implement it in different ways, but they all descend from that original idea.

In reply to a post by TinyMongomery:

All TCP/IP networking nowadays is built on the Berkley Socket interface, which originated in BSD 4.2. Different vendors will implement it in different ways, but they all descend from that original idea.

An API is quite different to an implementation, as I'm sure you're well aware.

In reply to a post by Pheasant:

Yeah I'm my own legal team. So my in-house general counsel had pause for thought, then gave me the nod. 🙈😂

PC Pro magazine had a good writeup on using Parallels to do this, and I see VMWare has their beta version out that does the same thing.

Of course they are different. The API is the important thing; the implementation doesn't matter. Programmers don't need to know how APIs are implemented.