From: rick_s on
On 6/27/2010 17:26, rick_s wrote:

> In the end we will have compatibility with any system since javascript
> works on all the popular machines.

For the complaining farmer theme example widget.

>
> Now this format is no good for the real AI assistant because their
> programming and behaviors are far more complex and the size of the code
> larger than a widget. That requires an overlord process written for the
> operating system, and the front man for that system is your AI assistant
> leader.
> His capabilities to manage networking and normal computer related tasks
> needs to be built in so that he or she can alleviate the workload and
> set you free in your 3D world or holographic world or Veldt.
> A more humanistic interface of some kind like giving directions to
> places in order to run your computer and all the tasks of the future
> which requires telling an AI assistant where to go, and in that way, you
> tell it what to do.
>

So then you are the Commander, you will give your AI assistant commands.

And so that he is not demeaned in front of the other people, like a
pageboy, you will tell him to go somewhere and get something.

So you can be standing in a crowd, talking to people and still tell your
AI assistant to do something private if you want and you don't have to
explain anything to him, just tell him where to go and on arrival trip
the macro to do some task.

So since you don't want to speak out loud even if necessary, then you
need something that can give him directions, like a pretend GPS.

In this way you can remember all the tasks you want him to do, by
storing tasks in objects in pretend rooms.
And then have bitmaps on file of these rooms as a reference and to
share, and when you share one, you share that task it contains, and at
that point it may be written in javascript or some other scripting
language like XML, or Shockwave Flash.

Maybe you will use C++ for commercial work, or Delphi or whatever the
market decides, and it will decide what is best for it.

Of course if someone creates 3D architecture we may do away with java
completely and use something else. Who can say what will happen when
everything changes like that.

Now the concept of a maybe boolean operator is not the same as declaring
a boolean variable called maybe and using that in 2D architecture.

True is a state, false is a state, and maybe is a state.

Maybe is neither true or false, it is undecided.

You can test to see if maybe is true or false though, but that's still
not making proper use of the maybe state, which will be used in
conjunction with the collapse of the wave function.

And like 2D architecture can fake 3D, you can fake a maybe, but the
complexity is such, that if you just do it properly, ok, and have 3
lines of iterating code, hey whats that billion lines of nonsense and
garbage you have everywhere trying to do that when the end result is not
as graphically real, on the screen?

Characters with feet that don't touch the ground like puppets from
Thunderbird XL5.

If you just use voxels and then you can easily work in 3D space, and
have the proper conditions so you don't need to fake things with a
billion lines of code and in the end end up with hollow framed
characters with weird hair.

Think about it.