VS Code كبديل

Written Explanation

An editor that grows into an IDE

VS Code starts as a fast, small code editor. It opens folders of files, highlights text, and has a built-in terminal. It knows very little about Java by itself. Its power comes from extensions: add-ons you install from within the editor. Microsoft's documentation recommends the Extension Pack for Java, a bundle of extensions that gives VS Code its Java abilities. According to that page, the pack includes:

• Language Support for Java by Red Hat (understanding your code, completion, error marks)
• Debugger for Java
• Test Runner for Java
• Maven for Java (a build tool, which you will meet later)
• Project Manager for Java
• Visual Studio IntelliCode (smarter suggestions)

A related option is the Coding Pack for Java, which bundles VS Code, a JDK, and these extensions in one installer. Per the same page, it is available only for Windows and macOS. If you already installed the JDK in lesson 2, you do not need it.

The JDK is still required

Extensions add help to the editor, but they do not contain a compiler. Microsoft's page says you must install a Java Development Kit to run Java in VS Code, and lists JDK sources such as Amazon Corretto, Azul Zulu, Eclipse Temurin, and the Microsoft Build of OpenJDK. The extension pack supports Java 1.8 and later, per that page, and for this course you use the baseline JDK from lesson 2. So the formula is:

VS Code + Extension Pack for Java + JDK = a Java environment.

If any part is missing, something specific breaks. Without the extensions you have a plain editor with no Java help. Without the JDK the extensions have nothing to compile and run with, and VS Code will tell you that it cannot find a Java runtime.

Installing and setting up

The steps are short. Menu names may differ by version.

1. Download VS Code from the official Microsoft site for your operating system, and run the installer. On Windows you may be offered options such as "Add to PATH" and adding "Open with Code" to the right-click menu. These are helpful, and you can accept them if you like.
2. Open VS Code and open the Extensions view. Search for Extension Pack for Java and install it. Microsoft's page also provides a direct link to the pack in the marketplace (its identifier is vscjava.vscode-java-pack). Install only extensions published by Microsoft or Red Hat for this purpose, and check the publisher name.
3. Make sure the JDK is installed. In a new terminal, run java -version and javac -version as in lesson 2.
4. Restart VS Code if you installed or changed the JDK while it was running. This follows the rule from lesson 3: a program gets its environment when it starts.
5. Optionally, run the Java: Tips for Beginners command from the Command Palette (open it with Ctrl+Shift+P, or Cmd+Shift+P on a Mac, and type "java tips"). Microsoft's page mentions this command as a first step.

Opening a folder and writing a class

VS Code works with folders, not with project files. The usual flow:

1. Choose File, then Open Folder, and select a folder, for example java-course/vscode-hello (create it first).
2. Create a new file in that folder and name it Hello.java. As in lesson 1, the name must match the public class, and you must see the real extension. The Explorer panel on the left shows the full name, so you will notice a stray .txt.
3. Write the class:

public class Hello {
    public static void main(String[] args) {
        System.out.println("Hello from VS Code.");
        System.out.println("Running on Java " + System.getProperty("java.version"));
    }
}

1. Run it. Microsoft's documentation describes a Run | Debug link, called a CodeLens, that appears above the main method. Click Run. You can also press F5, which starts the debugger, and the page says the debug configuration is generated automatically. Either way, the output appears in the Terminal or Debug Console panel at the bottom, depending on your settings.

The output is the same two lines you would get from javac Hello.java and java Hello in a terminal. In fact, you can do exactly that in VS Code's own integrated terminal, which opens in the folder you have opened. Do it once, and the connection between the editor and the commands becomes concrete.

Lightweight mode and standard mode

Microsoft's page mentions two working modes for Java in VS Code. Lightweight mode works with individual Java files and starts quickly. Standard mode loads the whole project and gives the full set of features, such as navigation across many files. For one-class programs, lightweight mode is enough. When you work on a project with several files and a build tool, VS Code asks you to switch, or you can do so from the status bar. The exact prompts depend on the version.

How VS Code finds the JDK

The Java extensions look for a JDK in several places. In general, they look at a Java setting in the editor, at JAVA_HOME, and at PATH, and they may also find JDKs in standard install folders. I could not verify the exact order on an official page, so do not memorize it. Use this practical approach instead:

• If it works, leave it.
• If VS Code says it cannot find Java, first check that java -version and javac -version work in a new terminal, then restart VS Code so that it sees the environment.
• If you have several JDKs and VS Code chooses the wrong one, look for the Java runtime configuration through the Command Palette (search for "Java: Configure Java Runtime"), or the Java settings. The command name is from my general knowledge, not from a page I opened, so use the search to confirm it exists in your version.

This connects directly to lessons 3 and 4: the editor is a program, it inherits its environment when it starts, and it can have its own setting that overrides the environment.

IntelliJ or VS Code: choosing

Neither is "better" in general. IntelliJ is the main tool in this course because the lessons show its screens, which makes it easier to follow along. VS Code is perfectly fine for learning Java. The rules of the language are identical, and the same programs run in both.

The one rule: pick one and stay with it while you learn. Switching tools whenever something goes wrong means you never learn either one, and each time you switch you rebuild the setup and may hit a different problem. You can learn the other tool later, when you know why you want it.