Servers, Hackers, and Code In the Movies
Billosaur writes "As with anything, Hollywood has a weird way of viewing computer technology and the people who use it. To help quantify things, take a look at The Top 20 Movie Hackers, the Top Ten Movie Servers, and the things code doesn't do in real life." From the servers article: "3. UNIX environment - Jurassic Park (1993). The UNIX environment here is a classic geek joke. Everything we saw was real - created by Silicon Graphics and called IRIX. InGen was the corporation funding the island, and from an IT perspective they let the worst possible thing happen: they allowed one programmer to design the infrastructure with no supervision. What's worse, they obviously required no documentation of what was done. The result was a kid had to hack in and gain ROOT privileges. The likelihood of a young kid knowing a way to get ROOT (and not a more experienced programmer) is pretty hard to swallow. The hardware for this server was probably minimal, running door locks and starting Quicktime movies. 'We spared no expense!' You would think that with the millions of dollars they spent on the park, they could have hired a couple newbie programmers and added a server on the backend."
The screenshot for Jurassic Park looks like a normal Irix screen. But what anybody who actually watched that part of the movie noticed was that the screen in the movie was some weird flying-through-a-virtual-reality-landscape thing, which the kid immediately recognized as UNIX. Almost everybody with actual UNIX experience just laughed at that, because it was classic a Hollywood computer representation. Except that it really was Irix, but running a window manager only available to people whose UNIX system had superfluous accelerated 3D graphics in 1995 (i.e., movie CG folks). What the audience couldn't see, but the kid would have been able to, was that the landscape had, written on the ground, things like "sbin" and "usr", clear signs of a UNIX system of some sort. As for breaking in, when dinosaurs are taking over your facility, chances are you aren't patching sendmail every day. And, in '95, that would have been a problem.
A statement:
I am a sound designer and a programmer. I have on many occasions intentionally, even without being asked, cut "blip" sound effects for code scrolling across a screen -- not just code, but any sort of stdout/text output/situational awareness display.
I do not do it because I'm stupid, or am trying to dumb down the audience, it for a few specific reasons:
We put blips on a computer screen for the same reason ipods chirp when you press a button. Psychology.
Don't blame me, I voted for Baltar.