Android Studio 3.1 Stable • Hacker News Board

Re: Android Studio 3.1 Stable

#21

Post by barbs » Tue, Mar 27, 2018, 8:39 AM UTC

dheera wrote: post #16

wpdev_63 wrote: 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.

What kind of ridiculous project structure do you have? I have never in my ~5 or so years of using Android Studio have had to do something as drastic as that.

I have occasionally have had issues with updating, but this has required a tweak in the gradle file and an update of build tools, at most.

Re: Android Studio 3.1 Stable

#22

Post by satysin » Tue, Mar 27, 2018, 9:06 AM UTC

I am surprised Google have not acquired JetBrains by now. Android Studio being based on their IntelliJ platform and Kotlin getting first class support in Android is investing a hell of a lot in a relatively small foreign company. Kinda strange as Google have acquired larger companies for less (less reliance not value).

Re: Android Studio 3.1 Stable

#23

Post by realharo » Tue, Mar 27, 2018, 9:08 AM UTC

satysin wrote: post #22

I am surprised Google have not acquired JetBrains by now. Android Studio being based on their IntelliJ platform and Kotlin getting first class support in Android is investing a hell of a lot in a relatively small foreign company. Kinda strange as Google have acquired larger companies for less (less reliance not value).

I really hope that doesn't happen.

Re: Android Studio 3.1 Stable

#24

Post by realharo » Tue, Mar 27, 2018, 9:19 AM UTC

clumsysmurf wrote: post #4

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.

To be honest, everything about Android seems like a bit of a mess to me - the APIs, the tools, plus all the things from the user's perspective.

Re: Android Studio 3.1 Stable

#25

Post by mundanevoice » Tue, Mar 27, 2018, 10:52 AM UTC

dheera wrote: post #16

wpdev_63 wrote: 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.

Okay. That's almost crazy. In my almost 3 years of maintaining our app that was originally written in Eclipse, we never had to face any single issues like this. There were some minor issues but never like this. It makes me wonder if the your project structure or the way project is written is crappy.

Re: Android Studio 3.1 Stable

#26

Post by chimprich » Tue, Mar 27, 2018, 10:59 AM UTC

realharo wrote: post #24

clumsysmurf wrote: post #4

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.

To be honest, everything about Android seems like a bit of a mess to me - the APIs, the tools, plus all the things from the user's perspective.

The official documentation is worse - everything seems to be a mess of contradictions and constantly changing ways of doing things, with the documentation never catching up.

Re: Android Studio 3.1 Stable

#27

Post by pjmlp » Tue, Mar 27, 2018, 11:01 AM UTC

mundanevoice wrote: post #25

dheera wrote: post #16

Earlier quoted context omitted.

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.

Okay. That's almost crazy. In my almost 3 years of maintaining our app that was originally written in Eclipse, we never had to face any single issues like this. There were some minor issues but never like this. It makes me wonder if the your project structure or the way project is written is crappy.

Well, just spend some time reading Android developer forums on Reddit, G+ or Google groups, every time there are new SDK or Studio stable releases.

The dheera is not alone.

Re: Android Studio 3.1 Stable

#28

Post by orf » Tue, Mar 27, 2018, 11:32 AM UTC

dheera wrote: post #16

wpdev_63 wrote: 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.

That is baffling, and probably down to your setup somehow. What exactly prevents it from compiling?

Re: Android Studio 3.1 Stable

#29

Post by mundanevoice » Tue, Mar 27, 2018, 11:37 AM UTC

pjmlp wrote: post #27

mundanevoice wrote: post #25

Earlier quoted context omitted.

Okay. That's almost crazy. In my almost 3 years of maintaining our app that was originally written in Eclipse, we never had to face any single issues like this. There were some minor issues but never like this. It makes me wonder if the your project structure or the way project is written is crappy.

Well, just spend some time reading Android developer forums on Reddit, G+ or Google groups, every time there are new SDK or Studio stable releases. The dheera is not alone.

Well, the rule of thumb is that if you need stability, never upgrade on the first day of release but rather wait for 1 week or two. I personally have faced and upgraded my apps through many of these upgrades and there was rarely an earth-shattering issue that I was not able to solve. YMMV.

Re: Android Studio 3.1 Stable

#30

Post by V-2 » Tue, Mar 27, 2018, 11:42 AM UTC

barbs wrote: post #21

dheera wrote: post #16

Earlier quoted context omitted.

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.

What kind of ridiculous project structure do you have? I have never in my ~5 or so years of using Android Studio have had to do something as drastic as that. I have occasionally have had issues with updating, but this has required a tweak in the gradle file and an update of build tools, at most.

My experience (full-time Android dev) falls somewhat in the middle.

This sort of compatibility breaking was fairly common back in the AS 1.X/early 2.X days. As of now, it's really rare, and usually resolves automatically.