Slashdot Mirror

← Back to Stories (view on slashdot.org)

Interview with Tron Creator Steven Lisberger

Posted by michael on from the glow-in-the-dark dept.

NeoCode writes "AintItCool has posted an interesting interview with the Tron creator Steven Lisberger. He doesn't talk much about the sequel Tron 2.0 (because of a Disney gag order) but he reflects about the original movie with nostalgia. He talks about what influenced Tron and what Tron meant (and still does) to people. Have a read."

5 of 205 comments (clear)

  1. Remind me. What was the Bit? by Anonymous Coward · · Score: 3, Informative

    "Remind me. What was the Bit? "
    The author sure did his research didn't he?
    Did he even watch the movie?
    Sure, the bit was a minor element in the movie, but come on.

  2. Tron 2.0 ?? by TheKubrix · · Score: 4, Informative

    I could be wrong but I believe it's called Tron Killer App

  3. Website.... by TheKubrix · · Score: 3, Informative

    Since the interview was a bit sucky, here is the official site for Tron 2.0, its got a pretty neat flash intro....worth a peek

  4. Re:What's up with the gag order? by Schnapple · · Score: 4, Informative
    What's with this Disney gag order?
    A few things, really. First, TRON 2.0 is really early into production, so no use in putting information out there that's potentially wrong. Second, lack of information at early stages makes for more tension and hype. But really part of it has to be based off of the idea that Disney may well pull the plug on the whole thing. A TRON sequel has been in the talking/development hell stages for years and years now.

    Monolith wanted their upcoming TRON 2.0 game to be based off of the sequel, but after waiting so long they gave up and persued (and won) the right to do up TRON 2.0 as a game, regardless of if the movie is made. Oddly enough, it looks like all the hype the game has created has made Disney more anxious to work on the movie, which is why we're hearing more and more about it.

    --

    Schnapple

  5. MCP=MS Windows by dillon_rinker · · Score: 3, Informative

    The MCP controlled access to the I/O system, or tried to. It died when a program got direct access to I/O. While it seemed to have the potential for much more, it spent a lot of its time on games. It obliterated other programs by absorbing their functionality. At its core, when everything else was stripped away, it had a teletype interface. Without it, the system had a lot more power (think CPU cycles). What it feared most was a debugging tool and it was destroyed by source code. (This last bit is clearly prophetic =)