Visual Studio Code is not an IDE, it's only a source code editor according to Wikipedia.
It's free, cross platform and can support a variety of different programming languages.
In looking at this once more I came across this posting VS Code versus Atom versus VIM versus Sublime.
So it is in the same realm as Sublime which was mentioned by Bear previously.
We have an FAQ about editors. You do need an editor which helps with indentation; you will find things so much easier with such formatting aids. Are you using Windows®? If so, I think the best is NotePad++, though I rarely use Windows® and there might be something newer.
salvin francis wrote:
Campbell Ritchie wrote:think the best is NotePad++, though I rarely use Windows® and there might be something newer.
I still use windows. Yes NotePad++ is still the best.
better than Atom.io or Sublime....doubful but a text editor is a text editor. They all do similar things just depends what you get comfortable with. Personally, I would rather write code in IntelliJ or Eclipse, but that's just because I am more comfortable with working in those environments.
Jericho Brown wrote:
ras oscar wrote:.. I am NOT looking for an IDE ...
Out of curiosity, why? Is there something you dislike about IDEs?
I have been trying to learn java on my own for a couple years. Worked with the Netbeans interface and continually got lost in my own code. Finally decided to go back to basics and do a few exercises from the command prompt. For me at my present greenhorn status, NetBeans simply removes me too much from the plumbing of java. I speculate I will return to Netbeans eventually, but I want to learn Java first.
Tim Cooke wrote:Conversely, I distrust any IDE to perform Maven and Git tasks reliably. As such I do all my Maven executions from the terminal.
I have that opinion of the J2EE version of Eclipse and its built-in Tomcat execution. But that's the fault of its WTP plugin. The sysdeo/mongrel plugin can run Tomcat properly.
The m2e plugin doesn't "perform maven tasks". It runs maven itself. It provides a profile template in the Run menu that facilitates Maven command-line options, such as selecting a goal, but Maven is a Java application and the plugin runs it as a Java application. It's quite straightforward. It doesn't screw around with Maven's run environment like the J2EE WTP plugin does with Tomcat.
The same, incidentally, is also true with Ant. git isn't a Java app, and I have found it a bit confusing at times, but then I find often git more than a bit confusing IDE or not.
Maven, in turn loves Eclipse. You can make a Maven project into an eclipse project just by running the command "mvn eclipse:eclipse" and then instructing Eclipse to add it to a workspace. If you're an IntelliJ fan, there's a goal for that as well.
Knute Snortum wrote:Even with the M2E plugin?
It's been a few years since I last worked with Eclipse, but I always found the M2E plugin crashed a lot and generally provided terrible support. It might have gotten better.
NetBeans' native support for Maven is excellent, but I make sure that I know how to perform everything from the command line as well. Same for tools such as Git.
If the Maven plugin only ran Maven, that would be good. But it also permits keeping multiple run profiles with differing goals, POM profiles, command-line options, etc. So you can quickly yank them off a menu and run them over and over again.
Plus it's good about incorporating dependencies into the project (both source and class) without requiring manual addition.
I'll admit that sometimes it seems to be mysterious about what it takes to make the light bulb go on, but mostly I think that has to do with the fact that Eclipse project facets are pretty gnarly to begin with.