Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Android Studio 2.0 Is Google’s New, Improved Development Suite

zco.com

Post reply on HN
Print view View original

21–30 of 78 posts

Re: Android Studio 2.0 Is Google’s New, Improved Development Suite

#21

Post by virmundi »

butz wrote: post #2

And it is still slower than good old Eclipse.

I know you're getting down voted, but I agree. In my experience, in both Windows VMs and on OS X, Intellij is just slow.

From the VM side, Eclipse compiled quick, Tomcat restarted great, JUnits flew. To be fair this was pretty straight forward Spring MVC/Services, no web plugins for HTML5 stuff. Intellij for Web Development (Gulp, and AngularJS support) was just terrible. The UI would be unresponsive. It could take multiple seconds for the File menus to pull up. Builds are slow. Hot deploy wasn't much better than in Eclipse.

On OS X, there's a typing lag. I could live with that. My big issue here is that Eclipse gets better battery life. There is a known bug in Intellij that forces OS X to keep the high performance graphics card on. Battery goes from 5 hrs to 2.5. This makes getting out of the house untenable. I use Android Studio because that's the guidance, but I prefer to not use Intellij if I can.

Re: Android Studio 2.0 Is Google’s New, Improved Development Suite

#23

Post by pjmlp »

butz wrote: post #2

And it is still slower than good old Eclipse.

Not only it is slower and takes piles of RAM, it still doesn't support the NDK properly, which keeps being experimental and lacks the majority of features that Eclipse CDT and ndk-build have.

Eclipse CDT with Ant + ndk-build finish a build before Gradle manages to parse all its configuration files.

Re: Android Studio 2.0 Is Google’s New, Improved Development Suite

#24

Post by pjmlp »

airless_cotton wrote: post #20
guelo wrote: post #18

Earlier quoted context omitted.

I don't think it's the IDE, it's the build system. When Google pushed everyone over to Android Studio they also pushed everyone from Ant to Gradle. Gradle is supposed to be a better Maven but it's just dog slow. Just typing gradle --help takes over 3 seconds on my Macbook Pro.

Migrating to sbt-android has been a revelation coming from Gradle. It's bizarre that a one-man-team beats the mighty Google in pretty much everything. The build is so freaking fast that it runs ProGuard by default – and beats a Gradle build without ProGuard. That dev implemented and shipped Instant Run way before Google "invented" it, and it's still faster compared to Google's implementation.

I really don't get their hype around Gradle, if it wasn't for it, most likely no one would care about Groovy any more.

Since my focus is the NDK, which keeps being half-done in Gradle, I keep using Ant + ndk-build and have migrated to Visual Studio 2015 for my Android hobby coding.

Re: Android Studio 2.0 Is Google’s New, Improved Development Suite

#25

Post by pjmlp »

HillaryBriss wrote: post #13
0xFFC wrote: post #6

Earlier quoted context omitted.

Not just slower , it does not fit to native look and feel, You are not going to believe me how much time I spent for fixing ridiculous font rendering for Android Studio, at the end I just gave up (in Ubuntu. I tried all kind of patches, TuxJdk, changing arguments for OpenJdk, OracleJdk , changing fontconfig, using infinality and anything you can imagine. nothing works). Right now I am switching to Xamarin,Perfect sup…

Yeah. There's something to be said for having a highly developed intelligence for building great IDEs and libraries at the _organization level_ rather than just at the individual programmer level. Despite its reputation for hiring the very best programmers in the world, Google's ability to create a really great developer toolchain for Android didn't measure up to what Microsoft has been doing for decades. It seems li…

If I would be on the Android team, I would feel ashamed that Microsoft in less time that they have introduced C++ support in Android Studio, already has a better developer experience than Google will ever managed to do.

On the other hand, I guess if they had a choice, the NDK would probably not even exist.

Re: Android Studio 2.0 Is Google’s New, Improved Development Suite

#27

Post by airless_cotton »

pjmlp wrote: post #25
HillaryBriss wrote: post #13

Earlier quoted context omitted.

Yeah. There's something to be said for having a highly developed intelligence for building great IDEs and libraries at the _organization level_ rather than just at the individual programmer level. Despite its reputation for hiring the very best programmers in the world, Google's ability to create a really great developer toolchain for Android didn't measure up to what Microsoft has been doing for decades. It seems li…

If I would be on the Android team, I would feel ashamed that Microsoft in less time that they have introduced C++ support in Android Studio, already has a better developer experience than Google will ever managed to do. On the other hand, I guess if they had a choice, the NDK would probably not even exist.

Yeah, it just shows that Google clearly sees app developers as sharecroppers. "Don't like our terrible software quality and negligence? GTFO, there are hundred other desperate people writing the same app."

Re: Android Studio 2.0 Is Google’s New, Improved Development Suite

#28

Post by cel1ne »

guelo wrote: post #18
butz wrote: post #2

And it is still slower than good old Eclipse.

I don't think it's the IDE, it's the build system. When Google pushed everyone over to Android Studio they also pushed everyone from Ant to Gradle. Gradle is supposed to be a better Maven but it's just dog slow. Just typing gradle --help takes over 3 seconds on my Macbook Pro.

Put

    org.gradle.daemon=true
in your .gradle/gradle.properties. Slow startup is an old JVM problem.

Re: Android Studio 2.0 Is Google’s New, Improved Development Suite

#29

Post by airless_cotton »

pjmlp wrote: post #24
airless_cotton wrote: post #20

Earlier quoted context omitted.

Migrating to sbt-android has been a revelation coming from Gradle. It's bizarre that a one-man-team beats the mighty Google in pretty much everything. The build is so freaking fast that it runs ProGuard by default – and beats a Gradle build without ProGuard. That dev implemented and shipped Instant Run way before Google "invented" it, and it's still faster compared to Google's implementation.

I really don't get their hype around Gradle, if it wasn't for it, most likely no one would care about Groovy any more. Since my focus is the NDK, which keeps being half-done in Gradle, I keep using Ant + ndk-build and have migrated to Visual Studio 2015 for my Android hobby coding.

As far as I know, sbt-android just recently got even more support/features for NDK (on top of the existing support):

The plugin can now manage and auto-install SDKs, tools, support repos and NDKs, so no messing around with Google's `android` tool anymore!

Maybe this is of use to you.

https://github.com/scala-android/sbt-android/commit/7b32e55f... https://github.com/scala-android/sbt-android/commit/53b855de...

Re: Android Studio 2.0 Is Google’s New, Improved Development Suite

#30

Post by airless_cotton »

HillaryBriss wrote: post #11
butz wrote: post #2

And it is still slower than good old Eclipse.

In theory, the new "instant run" feature addresses some of the "clean, build, deploy, run" pain. http://tools.android.com/tech-docs/instant-run In practice, what I've seen so far is that sometimes I'm not sure what is being "instantly run" -- my latest code change or something older. Still trying to gain confidence in that feature (or just not use it because I don't understand what it's deploying all the time).

Did you give https://github.com/scala-android/sbt-android-protify a try?

It exists longer than Google's "Instant Run", is faster and works without flaws (in my experience).

Post reply on HN