I think we agree completely: the main thing that is actually identical is the syntax of the language in which you program the system. That is an important similarity, and it makes it easy for Java devs to join the Android community. J2EE devs will find even further similarities. As you point out, JDWP works too.
On the other hand, Android runs on a completely different VM with very different rules for JIT optimization. The GC is very different and the concurrency rules are pretty different. Even from 50K feet, there are obvious differences (AWT, Intents, etc). When you get close enough to do actual development, the differences are substantial. -blake On Apr 27, 8:05 am, Cédric Beust ♔ <[email protected]> wrote: > On Fri, Apr 27, 2012 at 7:26 AM, blake <[email protected]> wrote: > > On the other hand, Android is substantially different from Java. > > Mmmh... in what ways exactly? > > It's 100% of Java "the language", most of the libraries (no AWT nor Swing), > perfectly integrated with IDEA and Eclipse (to the point where you can use > the debugger and put break points in your application while it's running on > the device). > > It has its own graphic library with, admittedly, a statically typed > resource system that will look a bit unusual to newcomers, but again, > that's nothing more than a framework doing things slightly differently, > like a lot of libraries in the Java ecosystem. > > I think one of the reasons for Android's success is precisely because Java > developers can get up to speed very, very quickly. > > -- > Cédric -- You received this message because you are subscribed to the Google Groups "The Java Posse" 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/javaposse?hl=en.
