Silicon Investor (SI) -- The First Internet Community

STOCKTALK

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.

Technology Stocks : Insignia Solutions (INSG) -- Ignore unavailable to you. Want to Upgrade?

To: Prognosticator who wrote (583)	1/27/1999 7:13:00 AM
From: Javaaah	Respond to of 1606

Prognosticator: HotSpot appears to be a very aggressive compiler, including the use of global dataflow analysis, and the necessary baggage that comes with it. This may make the compiler too memory hungry to get down onto small embedded platforms. There are also many technical problems to be solved if compilation is to continue once the allocated space for the host code is full ... I think that the JIT model grinds to a halt once this occurs, and the remaining methods are interpreted (not sure on this). Insignia are not using a JIT model based on their white paper. You're correct on 1.2. I haven't heard anything much on Pico-Java for quite a while. As for INSGY earnings, I have to agree with the humerous, well informed Irish fellah. Given the company is realigning itself for JENE, they wouldn't be expecting to see anything other than another loss (which was quite small) ... money's still in the bank, and they aren't predicting any JENE revenue until end of Q1. It'll be interesting to see what happens next between Sun and Insignia. If Sun gives Insignia the go ahead for Java badging, expect to see loads of JENE action!! Hopefully, we all get richer!! Javaaah

To: Prognosticator who wrote (583)	1/27/1999 2:56:00 PM
From: William Sheppard	Respond to of 1606

Prognosticator wrote: Why wouldn't HotSpot be relevant on consumer devices. Is it so large? Yes, primarily size. I don't know exactly how big it is, but I'm sure it will consume more memory (both object code and runtime) than can be comfortably provided on consumer devices given today's economics. Also only the full JDK's VM will be provided in a HotSpot version - there have been no announced plans to provide the technology for pJava or eJava. I'm a big fan of adding Java hardware support (probably adding it to a "standard" CPU core rather than a standalone JavaChip) for drastically improving performance at low cost. I think you'll see availability of this from several vendors this year or next as reported in EETimes and other places. I understand that Embedded Java is derived from JDK 1.1.7. I assumed that it would converge with 1.2 in the next rev (i.e. be a proper configurable subset of Java-2). Is this not correct? I don't believe I've seen any promises that Java 2 (1.2) and eJava will ever converge, although it's clearly in everyone's best interest to keep it as simple as possible. The real-time API will also complicate this, as everyone expects the Java language will need some tweaking to properly support real-time capabilities. Finally, what's up with Pico-Java: any recent news? The last I saw was from EETimes where someone was showing a settop box built with a PicoJava chip (from LG maybe?), and performance was excellent. Most of the licensees of PicoJava (LG, Fujitsu, NEC, IBM, etc.) plan to make the core available on a custom basis, I believe.