Many of us game devs use C++ for performance and especially cross-platform support, so I am very interested in seeing how NDK support turns out in this. Debugging native code in particular has always been a pain point even for people who don't hate Eclipse.
Introducing Android Studio
71–80 of 189 posts
Re: Introducing Android Studio
#72This 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.
Why does everyone seem to hate Eclipse? I've been using for a while and I can't find reasons to dislike it.
Have you tried visual studio or jetbrains? Even VS2005 runs circles around Eclipse Juno(2013).
Eclipse is slow, you have to manually edit memory-settings in eclipse.ini just to get bearable performance(-Xmx384m wtf??), it's buggy, plugins are confusing and often conflicting , the ui is bloated, intellisense is more in the way than it is helping, keyboard focus is all over the place when switching between panels(for example going between code/project/search). It's simply frustrating to work with it once you're used to something that actually works smoothly.
Re: Introducing Android Studio
#73This 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.
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 worse in every way outside of generally getting plugins/framework integration first.
and though i'm sure i could configure eclipse to behave the same way...out of the box intellij was very predictive for me. not just on obvious auto completes either. it seems to know what you want to do as you're typing. similar to the way BMWs communicate what's happening on the road to you and you begin to feel like you're one with the car. that level of interaction between me and the IDE makes it much easier to get code from brain to file imo
Re: Introducing Android Studio
#74This 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.
Why does everyone seem to hate Eclipse? I've been using for a while and I can't find reasons to dislike it.
There's been several projects where external forces have practically forced me into Eclipse (Android development among them). I dislike it because it's huge and difficult. It won't let me work simply. It is slow to start and slow to use. If I want to import a project, I have to manually copy the .project file and manually edit it because Eclipse is too retarded to just import a simple folder from the filesystem in anything like a sane manner. I have to tweak a bunch of crap in the messy menus and dialogs before I get a functional debugger, different for each project context. The UI is slow, meaning it loads slowly, and switching from Debug->Code view lags horribly. Using the internal windowing and docking system for widgets is hard and sometimes I have to reset the whole thing to get it back to a manageable place.
Those are my main complaints. I haven't used IntelliJ so I don't know if it is much or any better. I kind of feel like Eclipse exhibits the primary pervasive cultural philosophy amongst Java developers; create something massive and unwieldy, embed some useful functionality somewhere beneath layers of tedious boilerplate, and bundle it all up and act confused when no one wants anything to do with it. This is further exhibited by Java's attachment to XML, its packaging mechanisms (wars and jars everywhere), and its general verbosity.
I appreciate the intention behind all of this, but I think it's totally non-functional from an outsider's perspective. I hope IntelliJ is better.
Re: Introducing Android Studio
#75They're making it similar to developing Windows Phone applications, but in some ways even better!
The live preview of different layouts is FANTASTIC! I'm super excited!
Re: Introducing Android Studio
#76This 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.
Why does everyone seem to hate Eclipse? I've been using for a while and I can't find reasons to dislike it.
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.
Re: Introducing Android Studio
#77Download link?
Re: Introducing Android Studio
#78Many of us game devs use C++ for performance and especially cross-platform support, so I am very interested in seeing how NDK support turns out in this. Debugging native code in particular has always been a pain point even for people who don't hate Eclipse.
This will be make or break for me as well. I'm able to code C++ with Visual Studio (and Visual Assist X) and compile it directly in the IDE with vs-android.
The only thing that could make be switch over would be a robust NDK debugger.
Re: Introducing Android Studio
#79Earlier 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.
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/.
Re: Introducing Android Studio
#80Is 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!
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 default a config as possible and "import from" the build tool). then if you do need to start from scratch you lose very little (and don't add the eclipse metadata to git).