SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Microcap & Penny Stocks : Patriot Scientific - PTSC -- Ignore unavailable to you. Want to Upgrade?


To: Delite who wrote (4086)12/29/1997 5:42:00 PM
From: Jon Tara  Read Replies (1) | Respond to of 8581
 
"However, you still seem to be addressing the semantic gap between the patented PSC1000 architecture and the Java Virtual Machine which is very small."

The gap between the PSC1000 architecture and the JVM is not semantic - it is real. There *is* a gap, and the PSC1000 is not capable of running Java byte code unassisted and untranslated.

What *is* only semantic is the implication made by some (but not by Patriot!) that the PSC1000 runs Java byte code natively - it doesn't.

Yes, I have said before that, technically, the PSC1000 does "run Java byte code", as does almost every processor in existence. However, when you imply that it runs Java byte code natively, or when you imply that there is something unique about the PSC1000's ability to run Java byte code (as you did in your post), that is incorrect, and quite misleading.

If you to be accurate (you do, don't you? :) ) you should say something like "because the PSC1000 - like most microprocessors - runs Java byte code..."



To: Delite who wrote (4086)12/29/1997 5:46:00 PM
From: Jon Tara  Respond to of 8581
 
Oh, BTW, I missed the fact that the "semantic gap" comment was made in one of PTSC's press releases.

LOL! They are being honest and most people are missing the honesty! :) The "semantic gap", of course, isn't in the processor, but in the PR department. :)

To answer your last question, I don't know of ANY Java processor that is in silicon and available now. (Given that my definition - and I beleive the accepted definition - of a "Java processor" is one that executes Java bytecodes natively.)