Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Introducing Android Studio

plus.google.com

Post reply on HN
Print view View original

101–110 of 189 posts

Re: Introducing Android Studio

#101

Post by suyash »

dmiladinov wrote: post #25
davesims wrote: post #19

Earlier quoted context omitted.

IntelliJ 12's Android support is vastly superior to Eclipse, in addition to being just a better Java IDE overall. I'm now very curious to know just how different Android Studio will be from IntelliJ. 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.

Even the community edition[1] supports android development. Just point IntelliJ at your android sdk installation folder, and you're off to the races! [1]: http://www.jetbrains.com/idea/features/android.html

But I think this version is not the same as Android Studio community edition.

Re: Introducing Android Studio

#102

Post by omegote »

jonstjohn wrote: post #97

Looks great, too bad it won't even launch for me on Windows 7. Anybody else running into problems running it?

I was about to post the very same. W7 x64, try to launch the program, execution seems to create a crss.exe -> conhost.exe that hangs indefinitely.

Re: Introducing Android Studio

#104

Post by pablasso »

chaostheory wrote: post #85
davesims wrote: post #62

Earlier quoted context omitted.

The feature set is fine, and when it came out it was basically revolutionary. But over the years the architecture has developed real instability. Frequent crashes, terrible and fundamentally broken package/dependency management. Difficult to find features, inconsistent UX and a vast amount of very low-quality plugins in the ecosystem. Then there's the extremely varied and confusing set of packages. There's even a mat…

Everything you wrote was true several years ago, but today it's no longer true. Eclipse is pretty stable now since it has OSGI under the hood. UX wise though it's still pretty crappy. I wouldn't be surprised if the new Android IDE is still Eclipse.

> I wouldn't be surprised if the new Android IDE is still Eclipse.

The whole announcement is that it is based on IntelliJ.

Re: Introducing Android Studio

#105

Post by qwerta »

snaky wrote: post #79
qwerta wrote: post #76

Earlier quoted context omitted.

Have you tried Idea? :-) Anyway as IDE developer for alternative languages (Scala, Kotlin) I dont like Eclipse because they refuse to integrate any sort of support for third party languages. This has been going on for nearly a decade. Vmware had to basically fork JDT to build decent Groovy IDE.

Are you talking about some core Eclipse features that needed for third party language support? There are many amazing third language IDEs implemented as Eclipse plugins, not forks, like http://www.eclipse.org/koneki/ldt/ .

I am talking about languages which can crosscompile with Java source-code level. So class in Scala can be extended by Java class and again extended by Scala class and so on... By my knowledge this is AspectJ, Kotlin, Scala, Groovy and probably Ceylon

This requires deep integration with Java Development Tools to make incremental compilation working. And JDT team refuses this sort of stuff for nearly a decade now (since AspectJ). There are various hacks (such as aspect hooks used by Scala IDE). Probably best solution is JDT fork made by Spring Source (VMware) : http://blog.springsource.org/2009/07/30/a-groovier-eclipse-e...

And to add insult to injury Eclipse Foundation created their own language called Xtend. It has cross-compilation as well, but it first compiles down to Java source code and result Java code is than compiled by javac. Basically Java Preprocessor. (dont get me wrong. I really like Xtend as language, I just wish their team would put some pressure on JDT folks).

Re: Introducing Android Studio

#106

Post by krisc »

I've done one Android app for a college project using Eclipse a couple years ago. I've been wanting to get back into developing for the platform. Anyone have an opinion on a novice Android developer trying out an early access preview for this IDE?

Re: Introducing Android Studio

#107

Post by namityadav »

Taylorious wrote: post #87
king_jester wrote: post #58

Earlier quoted context omitted.

It's this, they said it was based on the community (free) edition of intellij.

That makes me angry. I really like Jetbrains as a company and you would think Google could spare some money and pay Jetbrains something.

This is massive for Jetbrains! We don't know whether some money exchanged hands at this moment, but Jetbrains is going to get a lot of value from the primary Android development platform being based on their product.

Re: Introducing Android Studio

#108

Post by davesims »

chaostheory wrote: post #85
davesims wrote: post #62

Earlier quoted context omitted.

The feature set is fine, and when it came out it was basically revolutionary. But over the years the architecture has developed real instability. Frequent crashes, terrible and fundamentally broken package/dependency management. Difficult to find features, inconsistent UX and a vast amount of very low-quality plugins in the ecosystem. Then there's the extremely varied and confusing set of packages. There's even a mat…

Everything you wrote was true several years ago, but today it's no longer true. Eclipse is pretty stable now since it has OSGI under the hood. UX wise though it's still pretty crappy. I wouldn't be surprised if the new Android IDE is still Eclipse.

My last full-time experience with Eclipse was a year and a half ago, and it was worse than it has ever been. Plugins and package management are a nightmare, and that's a quagmire that you can't simply rewrite your way out of. Terrible plugin quality control has created an entire ecosystem of bad Eclipse UI/UX.

As to OSGI -- that has been the core of Eclipse for nearly a decade, and IMO also a big part of the problem. The promise of OSGI was to allow Eclipse to be treated as a radically-open MDI framework that you could write just any old software on -- not just IDEs, but gaming frameworks, spreadsheet editors, on and on. The reality is that the standards for Eclipse's OSGI "drop-in" architecture have not stabilized into a robust ecosystem, rather it has lead to wildly varying user experiences, odd menu/pane/window configurations that have little consistency from one plugin to the next and poor quality software across the board. I'd be very reluctant point to Eclipse as an example of OSGI's fulfilled promise.

Also -- not sure if you read the OP, but the new Android IDE is going to be IntelliJ, not Eclipse.

Re: Introducing Android Studio

#109

Post by loso »

jonstjohn wrote: post #97

Looks great, too bad it won't even launch for me on Windows 7. Anybody else running into problems running it?

Thank you for posting this, I thought I was the only one and was going crazy. It is definitely not working for me on Windows 7 64.

Re: Introducing Android Studio

#110

Post by pjmlp »

andrewcooke wrote: post #80
pjmlp wrote: post #35

Earlier quoted context omitted.

I hate its workspace concept with passion. Most IDEs just use some kind of project file, or are able to use directly build tools. But Eclipse always has to create this workspace full of metadata that it likes to corrupt every now and then!

you can specify the workspace locn at startup (with -d iirc) so with an alias and/or some bash scripting you can use a separate workspace for each project (I have my projects in ~/proj as subdirs with commands to select which is current - although I only use eclipse for c dev work, intellij idea for java + python). also, use a separate build tool (eg ant) and don't store build info in eclipse (basically, use as defau…

All nice advices, except they don't work in Fortune 500 corporate environments where the tooling allowed in "your" computer is project dependent.
Post reply on HN