Dave Plummer

on a MIPS machine because it's unaligned.

So I'm having the argument that even though it's late and the Windows 95, they've already shipped one beta that we should now just guarantee that ID lists are always an even number of bytes or do some hack to just make sure this never happens.

So the code that references them on other hardware can just blaze through it.

And it became a shouting match and sort of a personal match and I lost that one.

And I still think that I know today that that code running on Windows is thousands of times slower than it has to be.

And nobody cares because it's plenty fast, but it could be a lot faster.

Well, about half your day is going to be spent debugging.

And most of that time is going to be spent in call stacks that are in pure assembly language because there's no source level debugging.

So it's not like we're in Visual Studio and you hit a breakpoint and it pops up and there's the source code.

You can go look at the source code, but you're looking at the raw assembly dump from the machine at all times.

Oh, man.

So it's a little cumbersome.

Better yet, we're doing four instruction sets because we're doing Intel, MIPS, Alpha, and PowerPC.

So depending on which machine it crashes on, you've got an entirely different instruction set that registers.

So you get reasonably adapted debugging all four, but...

I had more experience in MIPS, so MIPS stuff would come my way.

Yeah, I would say that 20% of my professional life has been creating and 80% has been debugging and fixing.

Yeah.

And I mean, I got a better reputation as somebody who could fix stuff.

And so stuff like that would flow to me.