I encourage devs (especially newer devs) to give each a go to see what suits their needs. Obviously there are many more points to touch on with each code editor but probably would take a bit more than a post to get to every point.Īll in all, my personal preference will always be IntelliJ. built on top of an Electron platform where as IntelliJ is running on an older JVM.
#Intellij vs vscode full#
many extensions to turn it into a full fledged IDE. good for working on single file or smaller things. indexes the entire project when you start up (speeds up search process ). version control to manage branches, browse changes, and merge conflicts. preferred IDE by new and experienced Java devs. Keep in mind this is a very small list from my point of view* What a long round-a-bout to get to the point of this post! Now that I have experience using all three code editors for Java development, I think I can give my opinion on learning curves and etc like that! I like to change it up occasionally at work and get experience. I have been back and forth using Eclipse and finally setting up VSCode for Java development. IntelliJ impressed me far more than I thought it would haha!įast forward to May of this year with the new job and here I have become comfortable with Eclipse. 
My choice was obvious at the time as I really didn't want to be stuck behind. I gave VSCode all of one day to get it set up for Java usage but Lambdas curriculum showed examples using IntelliJ. When I started out learning Java at Lambda, we could have used VSCode or used our student pack for a free year of IntelliJ IDEA.
0 kommentar(er)
