5 ms·

I'm not an Android developer, but I installed Android Studio a few nights ago just to play around with Android. I'm not sure where the author's coming from, bu

I'm not an Android developer, but I installed Android Studio a few nights ago just to play around with Android. I'm not sure where the author's coming from, but the IDE seems fine to me. I use IntelliJ at work, so that's what I'm used to. Maybe there's stuff that an actual Android developer would have issues with -- more advanced features, but I thought that the tool was leaps and bounds better than the Eclipse extension that used to be supported.

devopsproject 10y ago
> I'm not an Android developer...I'm not sure where the author's coming from, but the IDE seems fine to me You seem wholly unqualified to make this type of judgement
- mswift42 10y ago
  He's probably as qualified to make this type of judgement, as someone who opens Android Studio twice a year.
  - devopsproject 10y ago
    The author has 100% more experience than someone who opened it up one time last week for funsies.
    - endorphone 10y ago
      Do they? Nothing they've demonstrated shows that they do. But I will say that if someone is accustomed to A, and they are forced to use B for a short period, it is incredibly common for those users to bitch and gripe about how terrible B is simply due to lack of acclimation. The fact that they develop for Android infrequently makes their observations less valid to me, not more.
      - devopsproject 10y ago
        I'm saying someone who has tried to actually build a product using a particular tool has a lot more experience than someone who poked around for a bit. The author has legitimate grievances with the product confirmed by many comments in this thread.
        endorphone 10y ago
        Yet the people who report using it frequently have the most positive assessment of it. Shouldn't those people have the most relevant observations? Yes, Android Studio requires a lot of memory, but welcome to 2017 where entry computers have 8GB. Beyond that, their complaints are whiny "this is strange and unfamiliar and threatening to me" bullshit.
        devopsproject 10y ago
        No is saying anything even remotely positive about the gui editor. Gradle is extremely complicated. There are real complaints here.
Humdeee 10y ago
> but the IDE seems fine to me. What? How can you declare this after spending at most a few hours in the environment?
- manmal 10y ago
  I do mainly iOS development, fulltime for about 4y. Before that, I developed Android, mostly in Eclipse; so I know both worlds. And before Swift I actually preferred AppCode to XCode, which is also based on IntelliJ. XCode is stuck in the nineties, while IntelliJ is such a beast, functionality-wise. Sure, it's less snappy and the font rendering is bad, but if you can live with that, it will make you a better developer. You will start "intent driven" development, where you define algorithms with method placeholders first and only afterwards declare the methods. Your classes and vars will have better names because renaming is a joy instead of being a shot in the knee. You will get a better grasp of the architecture by looking at call hierarchies. You will never again miss an instance of a renamed method in some selector, because searching for references in AppCode is perfect. And you get all this with Android Studio, too. Let's not forget Kotlin, which might not even exist without JetBrains' involvement in Android Studio. BTW I sometimes fell back to XCode even when I was a heavy AppCode user, e.g. when the battery was running low. Switching is mostly seamless, because both watch the filesystem and seldomly complain about clashes. Perhaps one could use some lightweight Java editor alongside Android Studio, too?
- on_and_off 10y ago
  It does not seem like the author of the article has spent a lot of time with AS either.

devopsproject 10y ago

> I'm not an Android developer...I'm not sure where the author's coming from, but the IDE seems fine to me You seem wholly unqualified to make this type of judgement

mswift42 10y ago
He's probably as qualified to make this type of judgement, as someone who opens Android Studio twice a year.
- devopsproject 10y ago
  The author has 100% more experience than someone who opened it up one time last week for funsies.
  - endorphone 10y ago
    Do they? Nothing they've demonstrated shows that they do. But I will say that if someone is accustomed to A, and they are forced to use B for a short period, it is incredibly common for those users to bitch and gripe about how terrible B is simply due to lack of acclimation. The fact that they develop for Android infrequently makes their observations less valid to me, not more.
    - devopsproject 10y ago
      I'm saying someone who has tried to actually build a product using a particular tool has a lot more experience than someone who poked around for a bit. The author has legitimate grievances with the product confirmed by many comments in this thread.
      - endorphone 10y ago
        Yet the people who report using it frequently have the most positive assessment of it. Shouldn't those people have the most relevant observations? Yes, Android Studio requires a lot of memory, but welcome to 2017 where entry computers have 8GB. Beyond that, their complaints are whiny "this is strange and unfamiliar and threatening to me" bullshit.
        devopsproject 10y ago
        No is saying anything even remotely positive about the gui editor. Gradle is extremely complicated. There are real complaints here.

Humdeee 10y ago

> but the IDE seems fine to me. What? How can you declare this after spending at most a few hours in the environment?

manmal 10y ago
I do mainly iOS development, fulltime for about 4y. Before that, I developed Android, mostly in Eclipse; so I know both worlds. And before Swift I actually preferred AppCode to XCode, which is also based on IntelliJ. XCode is stuck in the nineties, while IntelliJ is such a beast, functionality-wise. Sure, it's less snappy and the font rendering is bad, but if you can live with that, it will make you a better developer. You will start "intent driven" development, where you define algorithms with method placeholders first and only afterwards declare the methods. Your classes and vars will have better names because renaming is a joy instead of being a shot in the knee. You will get a better grasp of the architecture by looking at call hierarchies. You will never again miss an instance of a renamed method in some selector, because searching for references in AppCode is perfect. And you get all this with Android Studio, too. Let's not forget Kotlin, which might not even exist without JetBrains' involvement in Android Studio. BTW I sometimes fell back to XCode even when I was a heavy AppCode user, e.g. when the battery was running low. Switching is mostly seamless, because both watch the filesystem and seldomly complain about clashes. Perhaps one could use some lightweight Java editor alongside Android Studio, too?
on_and_off 10y ago
It does not seem like the author of the article has spent a lot of time with AS either.