During production of Finding Nemo, we started using Linux boxes in addition to SGIs.
Why?

3D painting software we wrote for laying out coral was written in C++ using templates, and the debug info was too large for IRIX, but was debuggable on Linux.

Was this a 32 bit vs. 64 bit issue?

No.

IRIX reserved half the address space for the kernel, while Linux only did a quarter.

So on Linux, we had 3GB, and the symbols fit.

It was a 32 bit show, both machines had 4GB max.

Plenty for Finding Nemo.

How do I know this?

I was the project lead, although the best parts of it were written by my smarter collaborator Michael O’Brien (eventually SVP of R&D at Technicolor).

This story is *not* the 32 to 64 bit transition.

This is just us trying to get another GB of address space, where we leveraged the ongoing Linux port work w/alot of our own.

Now that I think about it, all the impactful work I’ve done in my career happened in 32 bits of address space.

4GB always seemed like a lot to me.

@Drwave I don't know if it's a certain vintage of worker or shared sensibilities, but this reminds me of a recent piece from my buddy Simo:

https://simo.virokannas.fi/2025/11/memories/

Also, these stories never get old. Keep 'em coming.

Memories

There was a time when software respected the machine it ran on. Developers measured memory in kilobytes, not because they were nostalgic minimalists, but because they had no choice. Code was writte…

Simo Virokannas
@isaact @Drwave Though not practical everywhere Command Line Text based browsers are really fast to use when you only care about text. I use for reading ebooks and some Reddit/Forum. They load pages so quick I often think they failed to load even though I know better now. Both Links (my preferred) and Lynx Browsers are good. https://links.twibright.com/
Twibright Labs: Links