Michael B. Johnson

@Drwave
2.8K Followers
668 Following
6K Posts
Yea, I'm the guy who used to work at Pixar and went to the MIT Media Lab. Still on the Board of the Cartoon Art Museum in SF. Come visit!

I give that preface to say that the one movie I went to see multiple times in a theater (that I bought tickets for and brought more people with me the second time) in several years was Sinners.

Made by local hero Ryan Coogler, I saw it at his local joint, Grand Lake here in Oakland near Lake Merritt.

I’m glad they got so many nominations, pleased they won a bunch of great ones liking writing and cinematography.

Anyway, if you haven’t seen it, give it a go.

Looking forward to owning a copy.

I love movies, I loved working on them, I own many on the highest quality media I can get my hands on over the years.

I do try and see them in the theater, but working at a movie studio for more than 2 decades, sometimes it’s easier, if i couldn’t see it at a studio screening, to just wait it out and watch at home on my Dolby Atmos 9.2 setup with choice of 70”+ OLED & 120” projector.

1/

@Bluedonkey totally agree.

But I tell this particular story because I expect folks today look at Finding Nemo (and the Pixar movies that preceded it) and don’t expect those were done on computers with less memory than pretty much every PC you can buy today.

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.

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.

@Gargron thank you.

RE: https://social.coop/@scottjenson/116239268805633372

I did honestly love this joke.

Still do.

@dmoren @gknauss will admit, took me a second…
@tess is that like shit post posting with tongue?