(product; not factor, damned gremlins..)

There are 100bn neurons in the human brain, each has upto 7,000 synaptic connections. You would need some factor of 10^14 bytes of RAM, assuming you're storing only one byte per synapse that's 636 TBs... Try again in 39 years?

Yes of course. I am assuming the only reason to refine Java Script on the server is to leverage revision across all platforms on the client side. After all, only a lunatic would choose Java Script as a server side language.

Java Script requires so many additions you might as well revise the whole strategy. Along with the next release of the Java Script, defining a standard web virtual machine on which JavaScript is initially implemented could provide many advantages:

- Develop using the same language in the browser as you are at the server.

- Translate classes or assemblies to and from the web VM using technology similar to JNBridge http://www.jnbridge.com/, opening to the door to all Java and .NET languages.

- An XHTML element could specify the URL for a compiler or interpreter, providing complete compatibility initially and opening the door to many possibilities in future.

Where is that now..?

I'm referring to programmatic interaction with the browsers DOM interface once the document is loaded.

Why? Primarily because Javascript is an awful language. As the emergence of GWT and countless other web 2.0 Javascript API's indicate, there is a lot of work being carried out in Javascript to bring more interactive UI to web pages. There are a number of advantages that introducing other languages thru a .NET or Java VM could bring:

- Javascript is not a language that scales well to larger teams and projects. It's loosely typed, not strictly OO, no standard documentation support, the list goes on.
- Staying within the browser DOM enforces more searchable, indexable semantic content.
- Allowing other server side CGI languages, like Ruby, Perl to interact with the same language on the client side.

Perhaps I'm a bit off topic, this could be more relevant on the Silverlight 3 thread.

Moving away from the DOM is ultimately going to confound searching engines and the namespaces they index. It would be nice to see Javascript running inside a VM - CLR or JVM, followed by other languages with the same access that Javascript has. Making Javascript a language under .NET in IE, perhaps using the Java VM for Javascript in Firefox etc. This may lend itself more readily to an indexable semantic web in the future.

If the computer is the generic machine: the Internet is the generic means of digital retail and distribution. But does anyone really want to prevent peer to peer file sharing?

I really wish they'd bring that show back.

I don't understand: how is it possible to acquire a company with technologies that are this monetize-able: http://tinyurl.com/dh8mcr ?