Back in the 90’s, during the waning years of the RISC-vs.-CISC rivalry which involved companies such as Intel, AMD, IBM, Motorola, and ARM, there was this one chip that was designed at AT&T’s Bell Labs that stood out from the crowd.
Unlike the other architectures, this processor was designed from scratch to flawlessly process instructions in C. This focus differentiated from other processors, all of which were focused on other priorities, not all of which benefitted the performance of programming language instructions.
Unfortunately, it never really caught on. It was used in AT&T’s EO Personal Communicator as well as the earliest versions of the BeBox by Be, Inc., but that was it.
Today, the big players from the 90’s are still beating their respective dead horses – AMD and intel with x86, IBM with POWER, and so on.
Yet, the rest of us have seemed to move on to bigger hardware requirements, such as higher processing speeds or graphics and networking.
So why can’t we try something new? Something modern and powerful enough to handle whatever we can throw at it?
Enter the JavaChip (beta).
This processor, in its imaginary conception, is built around, and optimized to run one of the two most heavyweighted programming paradigms of our time, Java.
This means that you can throw any possible application at it – in any programming language, such as C/++/# – and it will swallow it, digest it, and poop it out like yesterday’s prune juice.
You getting it?
Now, let’s say that we can have it used in at least 3 (THREE) processing units: Central, Graphic, and Network.
This would mean that the highest-end graphics, networking, and instructions processing known to man can be accomplished on a single personal computer.
And finally, what if this processor architecture was both free AND open source?
Think about it.
