81–90 of 104 posts
Earlier quoted context omitted.
The Sqlite debugger is also IDEA13 only I believe.
Isn't that the thing that requires the Ultimate Edition? That's why it is not in Android Studio.
Earlier quoted context omitted.
Are you doing "sbt idea" or "play idea?" From what I recall, "sbt idea" was broken, while doing it using the play launcher works, as they have some broken dependencies.
I use sbt idea. I can try play, but it would be great if it just worked.
(I am not saying this is a good idea, but I am saying it "just works".)
Earlier quoted context omitted.
IDEA Community Edition is free and perfectly usable
For what? Java SE? What else?
Other than "multi device preview" I think Android studio has all the features that IDEA13 offers for android developers. IntelliJ is great and I do all my Java/Groovy based development from it, but I'm not sure about buying the license just to go upgrade to 13
The more comments about IntelliJ IDEA I read, the more it reminds me of apple fans... It's just a tool and not a miracle! But hey, everyone is special and has the right to opinion, right? :)
Look at vim Vs. emacs for a better analogy.
Earlier quoted context omitted.
>> Things just work (subversion, Spring, hot swap). The same has been true for me in Eclipse for over 8 years.
Two things that do not "just work" first drove me away from Eclipse: a) git integration. Egit is bad and barely functional. I ended up abandoning it and doing all my git interaction at the command line. I rarely need the git command line with IDEA. b) Maven integration. We use a custom Maven setup that I could never get Eclipse to work properly with; it insisted on using a stock setup that could not build our project…
The lack of native development is one of the main things keeping me from giving IDEA a proper try. It may well be better than NetBeans, but NetBeans works well now, and has decent C & C++ support (at least as good as CDT, anyway).
I do have a personal license for IDEA 12, and would have no problem paying for an upgrade to 13 - it's just not worth my time (yet) to do so.
There are a few annoying bugs I've run into in NetBeans 7.4, and Android dev isn't awesome in NetBeans, so maybe there'll be enough impetus for me to give IDEA a real shot soonish.
Or the NetBeans bugs will get fixed, and I'll just stick tight. I'm happy either way!
The more comments about IntelliJ IDEA I read, the more it reminds me of apple fans... It's just a tool and not a miracle! But hey, everyone is special and has the right to opinion, right? :)
coding is our jobs. The IDE is our primary interface. Of course its important. Its much more of a vital decision than what looks good (apple fans), its about what gets the most real work done. Look at vim Vs. emacs for a better analogy.
All I'm saying is that the whole "it's worth paying extra", "it's so much better and productive", "it has so many features"... is just bs... IMHO. Use right tool for the job and be open minded, that's all. If I have to switch to go lang tomorrow, should I start complain, whine and wait for IDEA for go or just do whatever I have to do?
And you cannot compare vim vs. emacs anology with this one, since hey both are free and open source, however IDEA is just a good commercial product, but not a silver bullet, that's all.
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…
I'm curious to know what you like about gradle. A few months ago I had a chance to work with gradle and it looked to me like it was a step away from declarative project descriptions, back to writing loops to iterate through files, etc. Possibly I was using it wrong, but I've heard great things about it and perhaps my expectations were just too high.
Exactly why I like it. The delusion that build scripts are 100% declarative is one of those things that makes me hate tools like Ant etc. with a passion.
Parts of build scripts can be declarative, but the ability to break out and put imperative logic in some section where you need it is crucial. And the nice thing about Groovy (which Gradle is based on) is that you can usually do it in a very declarative way (eg: files*.delete() rather than looping, etc.)
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…
Um, what? I can think of plenty of times when I've needed to edit 9patches myself. Mind you, most of those times were when I was working in a startup, and we didn't have a dedicated UI/UX person, but this feature would still be incredibly handy.
The more comments about IntelliJ IDEA I read, the more it reminds me of apple fans... It's just a tool and not a miracle! But hey, everyone is special and has the right to opinion, right? :)
coding is our jobs. The IDE is our primary interface. Of course its important. Its much more of a vital decision than what looks good (apple fans), its about what gets the most real work done. Look at vim Vs. emacs for a better analogy.
Jeez, talk about responding to a fallacy with a fallacy...