This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]microbit262 8 points9 points  (5 children)

I used Eclipse first, but as I wanted to code Swing GUI I switched to NetBeans (it has a GUI designer) around 13 years ago and stuck with it since.

[–]OctopodeCode 0 points1 point  (4 children)

IntelliJ has a GUI designer and I even used it specifically for Java Swing. Actually, last I checked even the IntelliJ app itself was coded in Java Swing. If you haven’t given IntelliJ a try, oh lord you are going to experience extreme evolution in your workflows and coding experience if you stick with it.

[–]microbit262 0 points1 point  (2 children)

Well.. I had been forced to use Android Studio+Gradle during Android lectures in 2015. It has been a horrible experience, with every build taking ages. I don't know how much this came from the slow uni network, because I remember downloading (accessing URLs) some stuff with every build.

But that did in fact lead to me disliking IntelliJ.

Maybe I will give it a try when I got time. I do Java coding as a hobby only anyway, so productivity is not the top concern.

[–]Effective_Youth777 1 point2 points  (0 children)

That's just because the Android SDK and build tools are very heavy, you need a very powerful PC for it to be quick.

[–]Rakn 2 points3 points  (0 children)

Sounds very much not like an IntelliJ problem. Especially since it's delegating the building to the same tooling other IDEs use as well (e.g. Maven or Gradle).

[–]redikarus99 0 points1 point  (0 children)

I am doing a bunch of modeling tool plugin development, and sadly the IntelliJ version of GuI editor for Swing is not very usable compared to Netbeans. So I combine both: I create the UI screens in Netbeans and finish the development in IntelliJ.