Winsock

And then they arrived at, oh, wow, this network is bigger than the operating system.

What are we going to do? So they wrote this thing called Winsock.

which was the layer of abstraction that suited Microsoft's model of library coding, and it presented system calls up a level that basically looked like Berkeley Unix sockets.

Guy somewhere in Tasmania wrote this thing called Trumpet Winsock that was a complete implementation of how to do this.

pointing down into different cards.

You could get the NE2000, the ubiquitous network card of the 1980s and 90s.

The world was exploding into a universe of people running pretty much the same design powered by Unix.

Sockets.

So we developed IE3 as a set of components with APIs.

So if you want to integrate the page displayer in your app, in your own frame, or you wanted to use Winsock, or you wanted to use Communicate with a backend server in your own app.

So it was freed from...

the free from the browser and allowed any company to be able to build their own browser, their own internet enabled application.

And that was difficult, but I was like, oh, this is really interesting.

And then they put Winsock on a computer and that allowed you to do more stuff.

And then you could cobble together a browser and then Netscape decided to make access to a browser more accessible.

And then, you know, in the meantime, AOL has its own little network and it's behaving like a web thing.