Introducing Android Studio • Hacker News Board

Re: Introducing Android Studio

#171

Post by dodyg » Thu, May 16, 2013, 10:10 AM UTC

wsc981 wrote: post #17

untog wrote: post #2

This is huge. I've held out on Android development for many reasons, but my visceral hate for Eclipse is one of them. I know I've been able to use IntelliJ before now, but Eclipse was Google's example in tutorials, etc. Now I'm very excited to make an Android app.

Earlier this year I wrote my first Android app using Eclipse. After finishing the project, I decided I hated Eclipse enough to not waste any more time on the platform. I don't really like the Java language either, it somehow feels 'old'. But recently discovered Xamarin[1] and later this year will try to write an Android app again, but this time in C# using Xamarin Studio. I think it's a great alternative for Eclipse,…

It is going to be free since it is based on IntelliJ Community Edition.

This time around try use Kotlin(http://kotlin.jetbrains.org/) instead of Java. It offers 100% compatibility with Java and it works nicely with IntelliJ.

I wrote this fully fledge news app using Kotlin/Java https://github.com/dodyg/AndroidRivers

Re: Introducing Android Studio

#172

Post by njs12345 » Thu, May 16, 2013, 10:47 AM UTC

p_l wrote: post #119

Dove wrote: post #98

The early access preview ( http://developer.android.com/sdk/installing/studio.html ) is definitely prettier than Eclipse. Not that that's a high bar to clear. It also seems to be less stable, which is a high bar to clear. ;) Yeah, I know, pre-release software. The windows seem to take a long time to load, too. That strikes me as odd -- it's one thing when you're starting up some sort of interpreter, but several secon…

The long loading time might be unoptimized-yet parsing of various XML files of ones app. In general, it's mostly an evolutionary work on existing IntelliJ Android plugin. The View editor afaik has some support for custom views, but only some - it's rather iffy (IntelliJ Android view renderer simply used Android libs to render them, but of course that doesn't work for everything, and anything fully programmatic is dea…

In Eclipse you can use View.isInEditMode to hide code that doesn't work in the preview. Bit of extra work but probably worth it, having your custom views work in the layout editor can be a timesaver. I'd imagine that works in Android Studio too.

Re: Introducing Android Studio

#173

Post by qompiler » Thu, May 16, 2013, 11:02 AM UTC

werkshy wrote: post #144

ihuman wrote: post #43

Earlier quoted context omitted.

Why does everyone seem to hate Eclipse? I've been using for a while and I can't find reasons to dislike it.

Switching between tabs in the editor takes > 1s (on a core i7 with 12GB). That is enough to make it almost useless for me. IntelliJ community edition is much snappier.

I'm using Eclipse (Juno Service Release 2) for vanilla Java development and it doesn't even take a quarter of a second to switch between tabs and various perspectives. I'm using a first gen i3 with 4GB of RAM. Maybe there is something else wrong with your Eclipse setup?

Re: Introducing Android Studio

#174

Post by koalaman » Thu, May 16, 2013, 11:14 AM UTC

werkshy wrote: post #143

georgemcbay wrote: post #142

Eclipse is a constant source of small annoyances for me, none of which by itself is a huge deal but when taken together color my view of the editor negatively. Unfortunately, switching to Android Studio presents a different set of issues, like lack of Perforce integration (using Perforce is out of my control here, unfortunately). I'd assume some sort of hybrid Android Studio/IDEA setup is possible, but even still the…

I don't get it. Perforce is ~$200/seat/year. IDEA at $500 seems like a no-brainer compared to limping on with Eclipse.

Perforce plugin for IDEA is very buggy. I do not recommend.

Re: Introducing Android Studio

#175

Post by koalaman » Thu, May 16, 2013, 11:20 AM UTC

madoublet wrote: post #44

The BIG question in my mind is: will this work on ChromeOS?

no.

Re: Introducing Android Studio

#176

Post by Tomdarkness » Thu, May 16, 2013, 11:24 AM UTC

rpgmaker wrote: post #153

Dove wrote: post #98

The early access preview ( http://developer.android.com/sdk/installing/studio.html ) is definitely prettier than Eclipse. Not that that's a high bar to clear. It also seems to be less stable, which is a high bar to clear. ;) Yeah, I know, pre-release software. The windows seem to take a long time to load, too. That strikes me as odd -- it's one thing when you're starting up some sort of interpreter, but several secon…

Every time I open eclipse I feel like crying. Is just that awful (usability-wise). On my search to replace Eclipse for my android development I think I came across IntelliJ and it was very resources-heavy compared to eclipse which in the end made me give up on it. Let's hope it's more efficient now...

Make sure you disable any plugins you don't need for IntelliJ Idea otherwise it will just load every plugin for doing almost everything under the sun which can make it a bit bloated.

Re: Introducing Android Studio

#177

Post by sigzero » Thu, May 16, 2013, 12:05 PM UTC

chaostheory wrote: post #166

sigzero wrote: post #139

Earlier quoted context omitted.

Sorry, I cannot even take that comment seriously.

Why not? Do I sound insincere?

Because I have used eclipse and recently and I would not call it "stable".

Re: Introducing Android Studio

#178

Post by silon3 » Thu, May 16, 2013, 12:37 PM UTC

Zigurd wrote: post #65

ihuman wrote: post #43

Earlier quoted context omitted.

Why does everyone seem to hate Eclipse? I've been using for a while and I can't find reasons to dislike it.

Eclipse is a parody of a GUI. A GUI should offer you all and only the valid operations you can perform, depending on the selected object(s). Eclipse, far too often, offers to, e.g. deploy your Android app to a server. This kills discover-ability, especially for novices. It's like feeling around blindly in a box but every third thing is a hammer that bashes you on the knuckles. No. Fun. Eclipse comes off as a GUI past…

>A GUI should offer you all and only the valid operations you can perform

Visual Studio does this, mostly and it's way too annoying.

Re: Introducing Android Studio

#179

Post by praterade » Thu, May 16, 2013, 2:24 PM UTC

Does no one see that this is an obvious transition to make a proprietary Android dev environment?

Sure, Eclipse can be a little buggy, but it's FREE.

I'd rather take a free, third party IDE over something that will just push Google closer to world domination.

Re: Introducing Android Studio

#180

Post by JasonFruit » Thu, May 16, 2013, 2:32 PM UTC

madoublet wrote: post #44

The BIG question in my mind is: will this work on ChromeOS?

I don't mean to jump on you personally, but your question is typical of something I don't understand: why do so many people seem to want to do desktop-type things on ChromeOS? It's not meant for that kind of work, and there are plenty of other OSs that are.