On 12/09/2010 03:56 PM, CKoerner wrote:
http://www.androidpolice.com/2010/11/14/developer-interview-series-tweetdeck-for-androids-max-howell/
". Debug cycles on Android take half a minute at least"
I'm curious about that. Redeploying on Android is almost immediate, so I
think he's talking about compilation time? I'm using Maven, which is not
the fastest stuff around, and I'm just fine.
For what concerns the UI, he's right and the iPhone is cooler. BTW,
Android 2.3 seems to be a bit of a delusion for what concerns the L&F
enhancements.
"For example, the standard Android List View component is slow. So slow
that in the end—after trying for a while to wring some more performance
out of it—I wrote a custom implementation."
I have a strong annoyance feeling when I read "XYZ is slow" and then I
don't see the numbers and a reproducible test. For the record, I'm using
a ListView with 2000+ elements and it doesn't seem slow (on Android 2.1,
pre-JIT).
I agree that parts of the docs are poor.
I cant' comment on Eclipse, since I don't use it. Even in this case I'd
like to read something more detailed than "an endless source of
problems". I understand that Idea is better (I'm fine with NetBeans, but
I don't use any specific Android integration and unfortunately we can't
ask for an official Android support until the lawsuit is over), but I
find something curious that Eclipse is worse than XCode (see my previous
thread about refactoring).
--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
java.net/blog/fabriziogiudici - www.tidalwave.it/people
fabrizio.giud...@tidalwave.it
--
You received this message because you are subscribed to the Google Groups "The Java
Posse" group.
To post to this group, send email to javapo...@googlegroups.com.
To unsubscribe from this group, send email to
javaposse+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
