the scope changes done, but it's going to take until the second teusday
of next week."
Change takes time, and the more complex the system, the harder it is to
change it without breaking something.
Come to think of it, maybe that's the whole problem. Creating Neo
"broke" the Matrix, and sent Smith on a process-eating rampage across
the kernel.
--benD
Raymond Camden wrote:
> >
> > The problem with that idea is that, if the Oracle is a
> > high-level authoring program, why not build an army to take
> > care of Smith? For that matter, why not build herself a
> > subroutine to resist Smith?
>
> This is where I think the fuzziness comes in. We are so used to being
> able to just do *.* immidiately, and with no issues. (Ignoring the
> wonderful Windows "feature" that prevents you from deleting processes.)
> Imagine that if part of the whole AI thing is a _reduction_ in ability.
> That's not written very well. What I mean is - maybe to enable AI, you
> have to disable something else, like the core programs ability to
> _really_ be godlike and just do anything immidiately. So the God
> (Architect) is not quite "God" like. He can't just "delete process" on
> the good guys. He can't just drop the agents two feet from the good
> guys. I'm not sure if that makes any sense, and it's a bit of a cop-out
> as well. Of course, if the Architect could just delete *.*, there
> wouldn't have been much of a movie. ;)
>
> -ray
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
