Dusting off Android Studio. Upgraded a few things. The quality of the Android build tools is like Project Builder circa 2002. Really poor experience that Apple would never settle for, and Google shouldn’t either.
@manton I wish they partnered with someone like Microsoft and use Visual Studio for their IDE needs and not whatever deal they have with JetBrains.
But I guess we’ll have to do mediocre software by a mediocre company, shipping mediocre OS’s in a medioc… terrible IDE 😋
If they made their own IDE they’d probably kill it after a few months anyway.
…or combine it with a chat interface and call it Duo Hangouts.
@vincent Actually, chalk me up as someone who likes the IDEs from JetBrains. Well I would say that Android Studios is probably my lease favourite of the bunch (I think the actual Android dev stack is more the problem: millions of moving pieces that all that need to be upgraded every time you launch Android Studios such that it takes a frickin half hour before you can actually start coding), I do prefer it over the times when they used Eclipse as the IDE. At least there is a functional(ish) UI designer that allowed the use of the mouse. 😏
@lmika I see from this I was actually thinking of Eclipse, Not JetBrains or Android Studio. It’s been a long time since I did anything on Android…
@odd Yeah, Android development with Eclipse was rough. I'm not sure if JetBrains was around at the time or if they were trying to get Java devs by targeting the IDE most of them were using, but the experience was not great. Seemed very cobbled together. And I wasn't kidding about the UI designer. When the graphical interface actually rendered the UI — which was around 50% of the time — I had so much trouble trying to select and place controls with it that most of the time I gave up and just modified the XML directly instead.
@lmika I especially remember how slow the simulator was to load, and I was on a pretty specced machine.