Dave Plummer

And I got everything I wanted, but I wanted it to be really robust.

And so that, and small.

And the original was like 87K.

Okay.

You don't assume much, right?

If you're going to call the shell to run an app, well, that could be a network path that's on a TCP AP share that takes 90 seconds to time out.

So anytime you do any kind of API call like that that could take time, you're going to wind up doing it on a separate thread.

And so the app becomes a little bit more complex because everything is multi-threaded.

There's a couple of things that are a little hardcore now.

I'm surprised I did.

Like, I didn't want to link to the C runtimes at all.

So I made sure never to call a runtime call, and I didn't link to them.

And that saved me whatever the C runtime is, 96K or something.

So, you know, it almost doubled the size of the app if you just touched any C call.

So I was careful not to do that.

But then I was actually writing in C++, which is C with objects more than anything.

But...

In order to get it to work, I had to go through and call all the object constructors manually from the dispatch table and stuff because you don't have the runtimes to do it for you.

So you're working with a compiler that doesn't have its runtime, and I don't want to rat hole on the technical issues, but it's a lot of extra work to get it to work, but when you do, it's incredibly small and tight.

One of the cooler things that I saw is