Has anyone tried using Kotlin for Android development? (it's supposed to be lower runtime footprint than Scala, and it is officially supported by Jetbrains [1])
Kotlin works well for Android development. The annotations have gotten better recently, too, so you can interact with Android classes without too many null checks.
Version 13 is very awesome. We've been finishing our intellij plugin and are so close to having it be usable that it could be user ready in like 2 days which will be awesome because then I can spend more time using the new intellij. I'm also glad they fixed the git colors in the Darkula theme.
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.
> I could live with Eclipse though, despite SWT being also quite removed from the native experience.
How can SWT be removed from the native experience when it uses native widgets everywhere, as opposed to Swing, which reimplements them all in Java (the reason why Swing apps are so ugly and feel so non native)?
As someone who has used Eclipse, Netbeans and IntelliJ for years I can say that without a shadow of a doubt that IntelliJ is far ahead of the other two.
The only areas where Netbeans is ahead is built in tools for profiling tools and heap dump analysis, and wizard for visually creating a GUI. I can't think of a single area where Eclipse is better except perhaps number (but not quality) of plugins.
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
I really want to like Intellij since it is so much more responsive then Eclipse, but I can't for the life of me get a working scala set up in IDEA or in the community version. Eclipse might still be a bit of a sloutch, but it works.
What issues are you facing exactly? I've been successfully developing Scala apps since IntelliJ 12 with no issues. It's leaps and bounds better than Eclipse. One thing to note that for sbt-based projects, I recommend generating the IntelliJ project from https://github.com/mpeltonen/sbt-idea
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).
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-implemented Gradle "auto-sync" magic (http://www.sep.com/sep-blog/2013/10/17/android-studio-not-re...). Until then, it's still good ole' reliable Eclipse (I can't believe I just said that). Until a different IDE can support Robolectric and Robotium/Instrumentation tests in the same projct that can be run/debugged inside the tool and report results in a window (command line and html test reports don't count, sorry), I won't be switching.
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 stuff, even though we all used it for years and prefer it.
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.
> Things like the 9patch editor seem horribly misplaced (you probably don't want your devs to be editing those...)
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.
You probably know this already..if you hack up the build.gradle file you can get full android gradle builds in Eclipse, even testing and yes both ways..using regular android TDD with new espresso and Robolectric/Robotium.
I am confused about how the IntelliJ IDEA with android plugins competes with Android Studio. I thought that Android Studio is suppose to replace IntellyJ for android development.
Android Studio is built off of the codebase[0] from IntelliJ 13. The JetBrains products like RubyMine, WebStorm, and seem to be built off of the same core IDE with plugins for languages/platforms and features. So most of the functionality is really just in plugins, and of course IntelliJ probably offers additional Android development functionality for a price.
I really hope the Gradle support is ported to Eclipse and that the Eclipse Android tools are actively maintained. I tried Android Studio but it’s completely inaccessible with my screen reading software. Since it is based off IDEA I assume I would run into the same problem trying to use the new version so haven’t bothered.
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.
Personally I think "doesn't work like Eclipse" is a good thing. If you don't mind trying again go to http://www.jetbrains.com/idea/documentation/migration_faq.ht... first. You will also find CTRL+SHIFT+A combo useful - it's a fast search of settings/actions.
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.
Is the gradle support really better than in IDEA Community Edition?
Sure I can open the gradle.build file and edit it with syntax colorization but there is no smart auto-completion: you always see a giant list of objects, and not all of them are available.
The Gradle support is a part of Community Edition. Code completion should be available for dependencies and plugins (available in the Maven central). I've seen a few cases when there were no completion for the artifacts from the local Android repository. It will be fixed shortly.
I'd like to try an IDE, since I usually end up using vim due to the fact that my projects often mix languages (Python, C, Clojure, occasionally Scala). How do Intellij, LightTable, SublimeText, etc. perform on those sorts of polyglot projects?
I hear you, IDEA is awesome but quite heavy, most IDEs are today as they are built on languages that run on vms. I tend to have one heavy IDE and a lightweight text editor opened at the same time. That's the best solution.
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.
[+] [-] eranation|12 years ago|reply
[1] http://blog.jetbrains.com/kotlin/2013/08/working-with-kotlin...
[+] [-] ajselvig|12 years ago|reply
[+] [-] btipling|12 years ago|reply
[+] [-] coldtea|12 years ago|reply
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.
[+] [-] laureny|12 years ago|reply
How can SWT be removed from the native experience when it uses native widgets everywhere, as opposed to Swing, which reimplements them all in Java (the reason why Swing apps are so ugly and feel so non native)?
[+] [-] Omnipresent|12 years ago|reply
[+] [-] afsina|12 years ago|reply
[+] [-] switch007|12 years ago|reply
[+] [-] RivieraKid|12 years ago|reply
[+] [-] sigzero|12 years ago|reply
[+] [-] rdemmer|12 years ago|reply
[+] [-] ohwp|12 years ago|reply
[+] [-] pron|12 years ago|reply
[+] [-] sharprazor|12 years ago|reply
The only areas where Netbeans is ahead is built in tools for profiling tools and heap dump analysis, and wizard for visually creating a GUI. I can't think of a single area where Eclipse is better except perhaps number (but not quality) of plugins.
[+] [-] bestdayever|12 years ago|reply
[+] [-] Omnipresent|12 years ago|reply
[+] [-] yareally|12 years ago|reply
[+] [-] krschultz|12 years ago|reply
[+] [-] dkhenry|12 years ago|reply
[+] [-] dsaber|12 years ago|reply
[+] [-] TelmoMenezes|12 years ago|reply
[+] [-] hallucinating|12 years ago|reply
[+] [-] jebblue|12 years ago|reply
The same has been true for me in Eclipse for over 8 years.
[+] [-] swanson|12 years ago|reply
Android Studio is not really usable as an IDE if you want to have a fully featured test suite because of the weird, half-implemented Gradle "auto-sync" magic (http://www.sep.com/sep-blog/2013/10/17/android-studio-not-re...). Until then, it's still good ole' reliable Eclipse (I can't believe I just said that). Until a different IDE can support Robolectric and Robotium/Instrumentation tests in the same projct that can be run/debugged inside the tool and report results in a window (command line and html test reports don't count, sorry), I won't be switching.
[+] [-] lnanek2|12 years ago|reply
[+] [-] paperwork|12 years ago|reply
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.
[+] [-] barbs|12 years ago|reply
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.
[+] [-] fredgrott|12 years ago|reply
Yeah some blog posts are coming soon
[+] [-] bestdayever|12 years ago|reply
[+] [-] zidar|12 years ago|reply
[+] [-] 67726e|12 years ago|reply
[0] http://www.jetbrains.org/pages/viewpage.action?pageId=983211
[+] [-] RyanZAG|12 years ago|reply
[+] [-] bakerba|12 years ago|reply
[+] [-] jareds|12 years ago|reply
[+] [-] levosmetalo|12 years ago|reply
[+] [-] fridek|12 years ago|reply
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.
[+] [-] Chico75|12 years ago|reply
Sure I can open the gradle.build file and edit it with syntax colorization but there is no smart auto-completion: you always see a giant list of objects, and not all of them are available.
[+] [-] justafucker|12 years ago|reply
[+] [-] xinkr|12 years ago|reply
[+] [-] larve|12 years ago|reply
[+] [-] rogerthis|12 years ago|reply
E.g. http://youtrack.jetbrains.com/issue/IDEA-103320
[+] [-] unknown|12 years ago|reply
[deleted]
[+] [-] omarkatzen|12 years ago|reply
[+] [-] trollingineer|12 years ago|reply
I'm really glad Google is ditching Eclipse as the go-to IDE in favor of the IntelliJ-based Android Studio. Good riddance.
[+] [-] whizzkid|12 years ago|reply
[+] [-] computer|12 years ago|reply
[+] [-] tonyskn|12 years ago|reply
[+] [-] camus2|12 years ago|reply
[+] [-] octix|12 years ago|reply
[+] [-] tlarkworthy|12 years ago|reply
Look at vim Vs. emacs for a better analogy.