Re: Java's poor performance? Not really - pick the right tool for the job!
Johan Helsingius <[email protected]>
| Newsgroups | gmane.comp.hardware.microcontrollers.tini |
|---|---|
| Message-ID | <[email protected]> |
At 20:32 26/04/2004 -0600, Bruce Boyes wrote: > It's only "the same as C" if you compare it to a C interpreter which runs > on dozens of hardware platforms, and includes a broad array of tested and > robust, standards-based libraries. There is no such C beast. Remember - C has *no I/O* in its spec!! Ummh... I don't want to start a language war, but just in the name of acuracy, the C standard IO library *is* part of the spec. Yes, you won't find a C *interpreter* that runs on "dozens of hardware platforms", but you will find very good *compilers* (such as gcc) that run on hundreds if not thousands of systems. The reason to use java instead of C is not portability (and I think TINI is a good example of how java implementations differ) but the fact that it's all too easy to lose your hands and feet with the sharp edges of C (runaway pointers and memory leaks). Julf _______________________________________________ TINI mailing list TINI-6tN4nzCoH/[email protected] To UNSUBSCRIBE, edit your profile, or see list archives: http://lists.dalsemi.com/mailman/listinfo/tini