Live data from Hacker News

Android Studio 3.1 Stable

android-developers.googleblog.com

11–20 of 43 posts

Re: Android Studio 3.1 Stable

#11
post #8

Android Studio has such a fat ass. Every release it, and gradle, want more memory to do the same thing. I'm hoping that the tools devs improve or review the resource usage of the gradle plugin, etc. VS Code and the flutter tooling are svelte in comparison.

Yeah I agree that has been the case but lowering memory usage has been a target of recent for Android Studio - See https://developer.android.com/studio/releases/index.html#3-1... It's even using less memory than chrome lately.

Using less memory than chrome is the very definition of faint praise.

Re: Android Studio 3.1 Stable

#12
post #7
post #3

Earlier quoted context omitted.

I'm a JavaScript / typescript guy, so for me these past few years VS code has been leaps and bounds ahead of WebStorm w/ extensions,etc. But lately I've been using Datagrip for SQL stuff,and geez, did Jetbrain crush the competition w/ this product. ...once I switched the shortcuts to match VS Code's, that is

Could you elaborate? VS Code is faster/leaner than WebStorm, that's for sure, but are there any specific workflows that you feel VSCode is better than WS?

I found WebStorm a bit overwhelming when I first tried it (I was fairly new at the time), which made any workflow a little difficult for me out of the gate.

That, and I remember Staples of the JS ecosystem (eg ESLint) being somewhat difficult to set up. Maybe they were simple if one knew the Jetbrain workflows, but for me, esp. compared to VS Code, it seemed a huge undertaking just to get ESLint to work.

Actually, here's an SO question I posted awhile back about ESLint in WebStorm (well, intelliJ). This was shortly before I made the switch to Code.

https://stackoverflow.com/questions/34700062/intellij-plugin...

Re: Android Studio 3.1 Stable

#13
I was going to say that this is not a very big update but it brings https://www.jetbrains.com/idea/whatsnew/#v2017-3

and with it, type hints.

This should be very useful in kotlin with rx. map calls are often hard to follow without explicitly writing types.

This sounds like the best of both worlds.

Re: Android Studio 3.1 Stable

#14
I hope the memory enhancements show considerable improvements. I've seen people with >32 GB memory complaining that AS eating enough RAM to affect productivity.

Tip: If you have dual GPU system try launching AS, android emulator, Idea, WS, Pycharm, with the discrete GPU i.e (Linux/ATI in my case).

'DRI_PRIME=1 ../studio.sh'

bash -c "LD_PRELOAD='/usr/lib/libstdc++.so.6' DRI_PRIME=1 ../android-sdk/emulator/emulator -avd Nexus_5X_API_27 -gpu host"

I have seen considerable improvements in productivity for the same codebase with 3rd gen corei5 with ATI 7400M series GPU vs 7th gen corei5 with intel integrated gpu both having same memory. The OS setup is same.

Obviously, java by itself isn't using the VRAM; I assume the visual rendering of IDE's & emulators use it and leaves enough RAM for the AS to gulp.

Re: Android Studio 3.1 Stable

#15
post #3
post #2

Android Studio, and in turn, Jetbrain's IDE are an absolute godsend for productivity. Quick actions, macros, shortcut egornomics, etc. are top notch and make me a happy developer. I would even dare to say, it's a better IDE than Visual Studio. runs for cover

I'm a JavaScript / typescript guy, so for me these past few years VS code has been leaps and bounds ahead of WebStorm w/ extensions,etc. But lately I've been using Datagrip for SQL stuff,and geez, did Jetbrain crush the competition w/ this product. ...once I switched the shortcuts to match VS Code's, that is

+1 for Datagrip, use it everyday

Re: Android Studio 3.1 Stable

#16
post #2

Android Studio, and in turn, Jetbrain's IDE are an absolute godsend for productivity. Quick actions, macros, shortcut egornomics, etc. are top notch and make me a happy developer. I would even dare to say, it's a better IDE than Visual Studio. runs for cover

Almost every release of Android Studio has succeeded in breaking every single Android app I wrote. I have always had to cut and paste every class, resource, layout, one by one into a new project in order to get it to compile. I always fear pressing the "update" button.

Re: Android Studio 3.1 Stable

#17
post #2

Android Studio, and in turn, Jetbrain's IDE are an absolute godsend for productivity. Quick actions, macros, shortcut egornomics, etc. are top notch and make me a happy developer. I would even dare to say, it's a better IDE than Visual Studio. runs for cover

Yeah, when running on my gamer ring.

Android Studio's performance made me loose interess on JetBrain products.

Xeon class CPU, SSD and at least 16 GB RAM should be written on the box.

Re: Android Studio 3.1 Stable

#18
post #12
post #7

Earlier quoted context omitted.

Could you elaborate? VS Code is faster/leaner than WebStorm, that's for sure, but are there any specific workflows that you feel VSCode is better than WS?

I found WebStorm a bit overwhelming when I first tried it (I was fairly new at the time), which made any workflow a little difficult for me out of the gate. That, and I remember Staples of the JS ecosystem (eg ESLint) being somewhat difficult to set up. Maybe they were simple if one knew the Jetbrain workflows, but for me, esp. compared to VS Code, it seemed a huge undertaking just to get ESLint to work. Actually, he…

These days PyCharm (and as such, probably WebStorm too) just auto-configures itself to ESlint files if it detects it's installed.

Re: Android Studio 3.1 Stable

#19
post #17
post #2

Android Studio, and in turn, Jetbrain's IDE are an absolute godsend for productivity. Quick actions, macros, shortcut egornomics, etc. are top notch and make me a happy developer. I would even dare to say, it's a better IDE than Visual Studio. runs for cover

Yeah, when running on my gamer ring. Android Studio's performance made me loose interess on JetBrain products. Xeon class CPU, SSD and at least 16 GB RAM should be written on the box.

That's mostly Gradle. Jetbrains IDEs are not exactly lean, but Android's use of Gradle is an exercise in patience, even on the command line.

Re: Android Studio 3.1 Stable

#20

I hope the memory enhancements show considerable improvements. I've seen people with >32 GB memory complaining that AS eating enough RAM to affect productivity. Tip: If you have dual GPU system try launching AS, android emulator, Idea, WS, Pycharm, with the discrete GPU i.e (Linux/ATI in my case). 'DRI_PRIME=1 ../studio.sh' bash -c "LD_PRELOAD='/usr/lib/libstdc++.so.6' DRI_PRIME=1 ../android-sdk/emulator/emulator -av…

I've found that giving IntelliJ (or Android Studio) too much memory can actually backfire. The Java process ends up using all the memory you give it, but this also results in long GC pauses past a certain point. If you're curious, turn on the memory inidicator in the app with Settings -> Appearance -> Appearance -> Show memory indicator. I've found 2gb - 4gb to be the sweet spot depending on project size.
Post reply on HN