Live data from Hacker News

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

zco.com

31–40 of 78 posts

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

#31
post #24

Earlier quoted context omitted.

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...

Thanks!

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

#32
post #19
post #16

Maybe this is better left as a comment SO, but we have been unable to any recent version of Android Studio for our development team for the past four months because we use a mapFragment in our app. It's a known error [0] in the Maps API v2. I understand the complexity Google is facing, but I can't imagine Apple not addressing such a fundamental UI capability in their dev tools. Frustrating. [0] https://code.google.co…

For several months XCode would just crash when I tried to run my application with debugging. It was eventually fixed by an XCode update. I think the only large platform owning company that has really succeeded with development tools is Microsoft. With Microsoft's newfound interest in cross platform development I'm looking forward to the day when I can just develop entirely in Visual Studio.

> With Microsoft's newfound interest in cross platform development I'm looking forward to the day when I can just develop entirely in Visual Studio.

Agreed, VS is the best IDE out there by far. Still a shame that developing in VS implies developing on Windows.

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

#33

Earlier quoted context omitted.

Yeah I just started dabbling with it and I have an ultra fast windows 10 laptop with solid state drive and I'm amazed at how long it takes to go from changing a line of code to running it in the emulator. I was originally planning to do dev work for android in a virtual machine like everything else I work on but I doubt it would be anywhere near performant enough.

If you wanna feel something rare, find a win98 box on a pentium 2/3 and run turbo pascal IDE. Enjoy the paradoxical bliss. ps: TURBO.EXE amounts to a whopping 600KB.

LightSpeed C: modify-to-run in a couple of seconds (often).

I worked on an assembler/editor that had a change-to-run system on the order of a couple of seconds, too.

Something changes when you have near instant turnaround time. It's magic.

Some of the most miserable time I've spent has on projects with tooling where builds took hours, and often hours just to fail. I was even okay with 30 minute turnaround time, as long as it was clear that the bottleneck wasn't fucking lame tools: The need to burn a bunch of EPROMs for each build, for instance . . . though I fixed that as soon as I could.

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

#34
post #24

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.

It's a stretch to say Gradle "uses Groovy". In practise, it more like uses a tiny non-Turing Complete subset of Groovy.

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

#36
post #19
post #16

Maybe this is better left as a comment SO, but we have been unable to any recent version of Android Studio for our development team for the past four months because we use a mapFragment in our app. It's a known error [0] in the Maps API v2. I understand the complexity Google is facing, but I can't imagine Apple not addressing such a fundamental UI capability in their dev tools. Frustrating. [0] https://code.google.co…

For several months XCode would just crash when I tried to run my application with debugging. It was eventually fixed by an XCode update. I think the only large platform owning company that has really succeeded with development tools is Microsoft. With Microsoft's newfound interest in cross platform development I'm looking forward to the day when I can just develop entirely in Visual Studio.

Worked as a .net dev for ~3 years, and I loved VS, but it had its share of random problems too. I remember it flipping out and suddenly consuming a shitload of CPU and RAM for no apparent reason, even working on fairly small projects. It was nearly impossible to work with it until I switched to a more powerful PC.

Is it really fair to say xCode is not a successful tool? A lot of people use it, and I don't hear enough complains about it.

And what is the most common tool for Android development? I assumed it'd be Android Studio by now, is everyone still on Eclipse?

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

#37

Earlier quoted context omitted.

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).

Thanks. Will definitely look into it.

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

#38
post #16

Maybe this is better left as a comment SO, but we have been unable to any recent version of Android Studio for our development team for the past four months because we use a mapFragment in our app. It's a known error [0] in the Maps API v2. I understand the complexity Google is facing, but I can't imagine Apple not addressing such a fundamental UI capability in their dev tools. Frustrating. [0] https://code.google.co…

Have you ever used an Apple dev tool? If so, I'm shocked at how dramatically different your experience has been from mine. I would rank Apple absolute dead last in terms of caring about the usability of their dev tools out of any vendor of dev tools I have experience with.

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

#39
post #34
post #24

Earlier quoted context omitted.

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.

It's a stretch to say Gradle "uses Groovy". In practise, it more like uses a tiny non-Turing Complete subset of Groovy.

No, large parts of Gradle are actually implemented in Groovy. You're referring to the DSL, which can be used purely declaratively, but it's not limited to such use (you can use all Groovy language featured in Gradle scripts).

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

#40
post #26

Move fast, break all the tutorials. Android has a problem with churn in tooling.

Ive noticed this across the board with google with regard to developers. They half-ass everything programmers need to interface and use what they produce. Very frustrating.
Post reply on HN