Live data from Hacker News

IntelliJ IDEA 13 Brings a Full Bag of Goodies to Android Developers

blog.jetbrains.com

91–100 of 104 posts

Re: IntelliJ IDEA 13 Brings a Full Bag of Goodies to Android Developers

#91
post #87

Earlier quoted context omitted.

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.

What are you talking about? I use IDE everyday and I'm not questioning the importance of IDEs, i'm questioning the fan base :) 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 ID…

I don't think there will ever be silver bullets. :)

IntelliJ has a community version with the source posted over at GitHub. They also have a flavor for Python which recently had an open source version released. But as you said, to each his own.

Re: IntelliJ IDEA 13 Brings a Full Bag of Goodies to Android Developers

#92
post #14

Want to like IDEA, but using a Java (Swing) based UI, in both Mac and Windows, makes me always feel like when someones scraps a blackboard with his nails. I could live with Eclipse though, despite SWT being also quite removed from the native experience. At least it had bloody native text boxes and scrollbars and such.

How is this useless comment at the top?

It got there by expressing a common sentiment.

Now, what business does your content-less (and insulting to top) comment has on the thread at all?

Re: IntelliJ IDEA 13 Brings a Full Bag of Goodies to Android Developers

#93
post #39

Earlier quoted context omitted.

What do you see as the advantages of Eclipse over Intellij?

For me it's SWT - on Linux it's faster, the look & feel is consistent with the environment, and most importantly - font rendering. Fonts look really shitty in IDEA / Linux.

Recently using IntelliJ on Linux and fonts got better with this:

http://superuser.com/questions/614960/how-to-fix-font-anti-a...

Re: IntelliJ IDEA 13 Brings a Full Bag of Goodies to Android Developers

#95
post #56
post #45

Earlier quoted context omitted.

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…

Last I checked (October) I could not get the build.gradle to play nicely. Most of the other material online involved using instrumentCompile to trick Android Studio into running your unit tests and a custom runner/plugin: https://github.com/JakeWharton/gradle-android-test-plugin If you have gotten it working in Android Studio, I'd be very keen to see how (if you are willing to share).

I'd also be very interested in learning how to set up Android Studio to run Robolectric. Especially sinceone of the last releases removed the option to mark custom directories as test folders, so tat I now can't even use any Java features in the editor.

Re: IntelliJ IDEA 13 Brings a Full Bag of Goodies to Android Developers

#96
post #88

Earlier quoted context omitted.

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.

> a step away from declarative project descriptions 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…

When you run into the cases it is much better to write a plugin than to put imperative code into your build. Gradle builds are IMHO a huge step backwards for others trying to use someone else's build.

Re: IntelliJ IDEA 13 Brings a Full Bag of Goodies to Android Developers

#97
post #56
post #45

Earlier quoted context omitted.

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…

Last I checked (October) I could not get the build.gradle to play nicely. Most of the other material online involved using instrumentCompile to trick Android Studio into running your unit tests and a custom runner/plugin: https://github.com/JakeWharton/gradle-android-test-plugin If you have gotten it working in Android Studio, I'd be very keen to see how (if you are willing to share).

I followed: http://www.peterfriese.de/android-testing-with-robolectric/ I can't get it to run a specific (gives junit 3.8+ required error), but am able to run the whole suit.

Re: IntelliJ IDEA 13 Brings a Full Bag of Goodies to Android Developers

#99
post #88

Earlier quoted context omitted.

> a step away from declarative project descriptions 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…

When you run into the cases it is much better to write a plugin than to put imperative code into your build. Gradle builds are IMHO a huge step backwards for others trying to use someone else's build.

Really? You think someone will find it easier to go look at the source for my plugin rather than just a line of imperative code in my build script? I would agree it easily gets out of control, but I really don't think I would rather have to find and understand a whole plugin just to grok a one off piece of logic needed in the middle of a build script.

Re: IntelliJ IDEA 13 Brings a Full Bag of Goodies to Android Developers

#100
post #35

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…

Why not use Qt Creator?
Post reply on HN