Live data from Hacker News

Android Studio 3.2

android-developers.googleblog.com

81–84 of 84 posts

Re: Android Studio 3.2

#81
post #58

Earlier quoted context omitted.

Gradle is pure insanity. Take a JVM-based scripting language that no one uses, and base an entire build-tool around it - complete with a custom DSL - that is so slow it needs to be run in the background as a service to be even somewhat performant, and make sure that each new version somehow breaks older build scripts so that you're constantly being prompted to update, and then being prompted to fix whatever the updat…

Maven is very unintuitive though, at least Gradle does a better job on the CLI interface. Hopefully we'll get better options on the JVM in the future.

Honestly, I find Maven more intuitive. Gradle is too flexible, you can have dozens of way to perform one task. With maven, you often search for one plugin that does what you want and stick with that. Of course, if there's no existing plugin that fit you, then it gets much more complicated, but that case is usually rare due to maven's massive number of plugins.

Re: Android Studio 3.2

#82
post #5

Do the emulator and compiler still require SSDs and 16GB+ RAM to be usable? I love Android Studio but it used to always feel very heavy-weight.

Android Studio runs fine on my laptop (only with 8 GB RAM). And I don't use emulators, though. Just straight run the code directly on the devices.

Re: Android Studio 3.2

#84
post #65
post #59

Earlier quoted context omitted.

16Gb, Standard HDD, Mid range i5 processor. It's sluggish as hell. Takes an age to start up, the gui is slow, and compiling even a basic app taks forever, with much disk thrashing. I've given up, and recently uninstalled it. I'm going to try and develop android apps using Xamarin in Visual Studio instead (as I have that anyway for Windows dev).

I am on the same path, even though it makes me feel a bit like hypocrite given my advocacy for native tooling vs third party, it actually does seem a better path to sanity. Either that or just live with mobile Web and its constraints.

I often read complaints that Xamarin is buggy (builds randomly stop working, often need to restart Visual Studio, etc).

How's your personal experience with Xamarin? How's the tooling compared to Android Studio?

Post reply on HN