Introducing Android Studio
11–20 of 189 posts
Re: Introducing Android Studio
#12Re: Introducing Android Studio
#13If Google can make Android Studio good it's huge news for Android development.
Re: Introducing Android Studio
#14Re: Introducing Android Studio
#15Re: Introducing Android Studio
#16Re: Introducing Android Studio
#17This 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.
[1]: http://xamarin.com
Re: Introducing Android Studio
#18Re: Introducing Android Studio
#19This 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.
I'd guess it's going to something akin to the difference between JetBrains' RubyMine and Ruby/Rails plugin support inside IntelliJ -- same overall functionality with better UX integration for the domain.
Re: Introducing Android Studio
#20This 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.
I thought Google was pretty heavily invested in the Eclipse ecosystem, I think they use it quite a bit internally (at least from what I can gather). Perhaps those efforts were more in the interest of supporting the community of developers which use their API's, though. I also hate Eclipse, even though I've tried my hardest to overlook its shortcomings. I'll leave it at that so as not to delve too far off-topic.