81–90 of 189 posts
Is Eclipse worse or something when doing Android dev? It seems just fine to me doing normal Java dev, but to hear people talk it is the worst IDE ever invented.
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!
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.
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.
Earlier quoted context omitted.
I've used JetBrains' products in various forms (IntelliJ IDEA, Resharper for Visual Studio, and PhpStorm) for a long time, but every couple of years I was also exposed to Eclipse (Aptana Studio, and one or two other installs that I forget what they were for). Eclipse just feels clunky and not very well designed. Like they forgot to find someone to do UX work. Plus the workspaces concept is really stupid, and the vers…
Well said. I've used Eclipse for several years, and _never_ felt that it was lacking... except perhaps in the department of finding which permutation of pieces to install. Then, I installed PyCharm (a Python IDE from JetBrains which basically is IntelliJ for Python), and was BLOWN AWAY by the polish. It's not that it's faster. That helps. The thought that was put into how you can make it your own -- search boxes on t…
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.
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…
Earlier quoted context omitted.
I wonder if they've licensed something from JetBrains or if this "IDE" is an extensive plugin on top of the free version of IntelliJ.
It's this, they said it was based on the community (free) edition of intellij.
Early access preview available now: http://developer.android.com/sdk/installing/studio.html
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.
This is pretty crazy considering the huge investment Google has made into Eclipse to create the SDK there. There is also a significant community investment in using Android with Eclipse. Eclipse once you get rolling is amazing, and most importantly its free which is a big deal especially to cash strapped individuals and businesses. What will happen with the existing Eclipse SDK? Also what about GWT? Splitting the IDE…
Is GWT still even a thing they care about? It seems like they're pushing people towards Dart and Angular at this point.
I/O last year was seriously thin on GWT, and it looks this year like there's only one session, which got misfiled in the schedule under "Google Wallet."