Write once, debug everywhere.
Posted on:June 08 2005
Currently I'm struggling with a Java application which runs only almost everywhere. I understand why Java is a slow, memory swallowing language. (BTW: I mean, 512 MB to make a java text editor usable? A 3D world with millions of polygons displayed in realtime and written in C++ can fit into there, and it will run faster than that crappy Java IDE.)
Java compensates this with its "write once, run everywhere" paradigm. But it is really horrible if even this doesn't really work. The program our team is working on runs on all our machines. But, of course, not on the presentation PC. Ok - it runs, but it has slight differences: It doesn't show any icons.
Yeah, that's cool. I tried out nearly everything now, it looks like it is really the fault of the JRE. Who said that developing database frontend applications is boring. :)
|Link ||[url] www.example.com [/url] |
|Bold ||[b]bold text[/b] |
|Quote ||[quote]quoted text[/quote] |
|Code ||[code]source code[/code] |