News for hackers. Stuff that matters.
Re:Jurassic Park computer system in the browser by bhouston on Monday March 03, 2014 @09:27AM (#7333837)
SGI IRIX operating system: http://en.wikipedia.org/wiki/IRIX

I used that at my first programming internship at university. Even then (1999) it was a dated OS, but it was still fun it.

I wonder if they used IRIX in the movie because the VFX guys making the movie, ILM, were doing all the VFX work using Softimage on SGI machines running IRIX at the time.

Re:Jurassic Park computer system in the browser by ghaff on Monday March 03, 2014 @12:28PM (#7334995)
Apparently the specific "It's a Unix system" scene used an experimental fsn (file system navigator) that SGI developed but which was never released as a product.
Re:Jurassic Park computer system in the browser by fit2rule on Monday March 03, 2014 @12:47PM (#7335116)
It was released on one of the Indie demo disks that SGI liked to hand out at conferences and subscribers and so on .. the source is still around, and of course there are a few clones by now: http://fsv.sourceforge.net/
Re:Jurassic Park computer system in the browser by mhurron on Monday March 03, 2014 @01:11PM (#7335276)
It was included with IRIX 5 but dropped in IRIX 6.
Re:Jurassic Park computer system in the browser by vidarh on Tuesday March 04, 2014 @08:50AM (#7340108)
It was released. The university I went to had a computer lab full of SGI Indy's that they'd gotten really cheap from the distributor, and they all had the 3d navigator installed.
Re:Jurassic Park computer system in the browser by angersock on Monday March 03, 2014 @12:34PM (#7335042)
Yeah, good memories.

SGI machines were beautiful, full stop.

Re:Jurassic Park computer system in the browser by michael_h on Monday March 03, 2014 @01:14PM (#7335299)
I have an SGI Octane at home. It weighs 55 pounds.
Re:Jurassic Park computer system in the browser by sdfjkl on Monday March 03, 2014 @09:49PM (#7338130)
It was also extremely repairable compared to modern computers. Everything was modular and upgradeable, including the CPU board, which just slid out of the machine on a lovely tray.
Re:Jurassic Park computer system in the browser by angersock on Monday March 03, 2014 @10:23PM (#7338249)
And the forced-air cooling was a work of art!
Re:Jurassic Park computer system in the browser by SimHacker on Tuesday March 04, 2014 @12:05PM (#7341455)
When I was working at UniPress in New Jersey, we had an SGI Iris. Those things are fucking heavy! It was raining outside and the office started to flood, so we had to keep taking shelves down off the wall and wedging them underneath the Iris to jack it up above the water, as it kept getting deeper and deeper.

The Indigos were another story entirely: They couldn't touch the raw graphics performance of an Iris, since the rendering was all in software, but you could actually stuff one of them in the overhead compartment on an airplane!

And then there was the SGI Indy... They made up for being small on the outside, by being HUGE and BLOATED in the inside:

"Indy: an Indigo without the 'go'". -- Mark Hughes (?)

This legendary leaked memo has become required reading for operating system design courses:

http://www.art.net/~hopkins/Don/unix-haters/tirix/embarrassi...

Software Usability II October 5, 1993 Tom Davis

Last May, I published my first report on software usability, which Rocky Rhodes and I presented to at Tom Jermoluk's staff meeting (with Ed, but without Tom). Subsequently, I made it available to quite a few other people. This sequel is to satisfy all those people who have urged me to bring it up to date. I begin with a summary; details follow.

Please read at least the summary.

SUMMARY

Release 5.1 is a disappointment. Performance for common operations has dropped 40% from 4.0.5, we shipped with 500 priority 1 and 2 bugs, and a base Indy is much more sluggish than a Macintosh. Disk space requirements have increased dramatically.

The primary cause is that we attempted far too much in too little time. Management would not cut features early, so we were forced to make massive cuts in the final weeks of the release.

What shall we do now? Let's not look for scapegoats, but learn from our mistakes and do better next time.

A December release of 5.1.2 is too early to fix much -- we'll spend much more time on the release process than fixing things. Allow enough time for a solid release so we don't get: 5.1.2.1, 5.1.2.2, 5.1.2.3, ...

Let's decide ahead of time exactly what features are in 5.1.2. If we pick a reasonable set we'll avoid emergency feature cuts at the end.

Nobody knows what's wrong -- opinions are as common as senior engineers. The software environment is so convoluted that at times it seems to rival the US economy for complexity and unpredictability. I propose massive code walk-throughs and design reviews to analyze the software. We'll be forced to look closely at the code, and fresh reviewers can provide fresh insights.

For the long term, let's change the way we do things so that the contents and scheduling of releases are better planned and executed. Make sure marketing and engineering expectations are in agreement.

INTRODUCTION

We've addressed some of the problems presented in the original May report, but not enough. Most of the report's warnings and predictions have come true in 5.1. If we keep doing the exact same thing, we'll keep getting the exact same results. I'm preparing this report in ASCII to make it widely available. It's easy to distribute via news and mail, and everyone can read it.

An ASCII version of the May 12 report can be found in:

bedlam.asd:/usr/tmp/report.text

The included quotations are not verbatim. Although the wordings are inexact, I believe they capture the spirit of the originals.

BLOAT UPDATE

"Do you want to be a bloat detective? It's easy; just pick any executable. There! You found some!" -- Rolf van Widenfelt

[...] Read the rest at: http://www.art.net/~hopkins/Don/unix-haters/tirix/embarrassi...

Re:Jurassic Park computer system in the browser by rrhyne on Monday March 03, 2014 @11:31AM (#7334634)
I recognized it as well from working in SoftImage, PowerAnimator (became maya) and Houdini on these systems.