-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 8/13/10 11:39 , Miguel Morales wrote: >> I don't know of any popular fast java applications, despite all >> these features. Again, Java is ok, great for what it does. But >> > just not as good as its alternatives. It's great for android > because it's popular. It's stable, there's tons of libraries, it's > fast/efficient enough. You can optimize the hell out of it. > That's why I said it's ok to good. When was the last time you > heard of java in the news or in anything interesting until recently > with android? Like I said, Oracle should be grateful google chose > to use java. > Java on customer desktop applications has been limited by a number of things that you previously cited: it's hard (but not impossible) to get a native look and feel, and for many years in the past it was even difficult to get a decent look and feel, and for many years there have been hard times in deploying it easily (there are still some residual problems). These are important things if you have to reach the end customers. In the industrial world, where both issues are less important, Java is widespread. Just have a look at http://platform.netbeans.org/screenshots.html and http://eclipse.org/community/rcp.php. You'll find tons of applications made even by large corporates and for basically all the industrial segments, running on the desktop. These are only the subset of Java applications using the NetBeans Platform and Eclipse RCP technologies - - there are many others. And these are only those that the makers were available to speak on; for instance, I've been consulting for years also on Java on the desktop and have customers running large and business applications which are 100% Java, also on the desktop, but aren't interested in publicly talking about them. Also, industrial applications don't make easily through common news as customer applications do, and this explain why Java is not well known to the large public.
Yes, Java needs more memory in comparison with C. So, what's the point? It's a matter of cost / benefit ratio and memory is cheap enough to wholly compensate the increment in productivity that one has by working with the whole Java ecosystem (which include tools heavily based on bytecode manipulation, such as profilers, AOP, coverage reporting tools, etc...) that aren't in the domain of C because it compiles to native code. For what comes to Android, I'd like to recall that up to 2.1 we didn't have any JIT, that has been introduced with 2.2. I'd be curious to know whether people who has experienced some performance troubles with Dalvik has tried his app on Froyo. - -- Fabrizio Giudici - Java Architect, Project Manager Tidalwave s.a.s. - "We make Java work. Everywhere." java.net/blog/fabriziogiudici - www.tidalwave.it/people [email protected] -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxlFnYACgkQeDweFqgUGxempQCdEzt80ZrbqIWWdVB8WP7gsHMA 82YAoIgv2TyivL70dfjQNtpbk+SqHovH =R0Su -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
