51–60 of 104 posts
I just recently started doing some Java development (despite vowing never to again), and one of the reasons I'm kinda cool with it is Intellij. Intellij makes it way easier. Things just work (subversion, Spring, hot swap).
>> Things just work (subversion, Spring, hot swap). The same has been true for me in Eclipse for over 8 years.
[1] http://blog.jetbrains.com/kotlin/2013/08/working-with-kotlin...
After trying to use Android Studio with its Gradle integration behind a company firewall that requires all outside network access through the proxy, I just gave up and went back to Eclipse, where everything just works. Diving through different configuration options was just to painful to put up with.
Properly set IntelliJ will boost your productivity many times. It's just an investment if you migrate from other IDE. I like to think about it as something similar to migration from crappy unit testing solution to a better one - it just pays off after some time.
The only feature that really excites me is the Gradle support. Things like the 9patch editor seem horribly misplaced (you probably don't want your devs to be editing those...) and others seem so situational (the autocompleting sdk version - a one line config value that you set once per project). Android Studio is not really usable as an IDE if you want to have a fully featured test suite because of the weird, half-im…
Weird, I know we have Robotium and Robolectric working fine in Android Studio at work. Although some versions do require a separate project, most versions are just sub-projects under a main folder with a shared build.gradle now. Not than any of us want to use it. You are just forced to if you want to use the latest features like AARs with Gradle. Eclipse is unfortunately obsolete and incapable of handling the latest…
If you have gotten it working in Android Studio, I'd be very keen to see how (if you are willing to share).
The only feature that really excites me is the Gradle support. Things like the 9patch editor seem horribly misplaced (you probably don't want your devs to be editing those...) and others seem so situational (the autocompleting sdk version - a one line config value that you set once per project). Android Studio is not really usable as an IDE if you want to have a fully featured test suite because of the weird, half-im…
Like maybe idea 13? That's how we do it at least.
Earlier quoted context omitted.
Not really actually. With the free community edition, you only get to manage "java" which doesn't work for me since i work with different programming languages with lots of front-end stuff as well. I meant to use it from editing xml, css, html to configure tomcat settings for example. On the other hand, i totally understand that they want people to buy it for fully featured version.
Eclipse is fully featured and professional and free as in beer and software.