Java开发者咨询：javac <file>与java <file>的差异，以及javac <filename>、java <file_name_without_extention>与java <filename>的区别

Hey there! Let's unpack these two Java toolchain questions clearly—they're fundamental to getting comfortable with running Java code.

1. Core Differences Between javac <file> and java <file> Commands #

These are two totally separate tools in the Java Development Kit (JDK), each with a unique job:

• javac <filename>.java: This is the Java compiler. Its sole purpose is to take human-readable .java source code files and convert them into platform-independent bytecode stored in .class files. For example, running javac HelloWorld.java will spit out a HelloWorld.class file if your code has no errors. It doesn't execute anything—it just prepares your code for the JVM.
• java <classname>: This launches the Java Virtual Machine (JVM), which executes the pre-compiled bytecode from .class files. Important note: you don't include the .class extension here—you pass the actual name of the class that contains the public static void main(String[] args) method. So if you have HelloWorld.class, you run it with java HelloWorld. The JVM finds and loads the bytecode, then runs the main method as the entry point.

2. "Compile First, Then Run" vs Directly Running java <filename>.java #

This difference hinges on which version of Java you're using:

• Before Java 11: You had no choice—you had to run javac <filename>.java first to generate the .class file, then use java <classname> to execute it. Trying to run java <filename>.java would throw an error, since the JVM expected a compiled class name, not a source file.
• Java 11 and Later: A feature called Single-File Source-Code Programs was added. Now, running java <filename>.java does two things behind the scenes:
  1. It compiles the .java source file in memory (no persistent .class file is created on your filesystem).
  2. It immediately runs the compiled bytecode via the JVM.
• Key practical differences between the two approaches:
  • Persistence: javac creates a .class file you can reuse—you can run java <classname> as many times as you want without re-compiling. The direct java <filename>.java approach re-compiles every time you run the command.
  • Complexity: If your code relies on other .java files or external libraries, the direct java command won't work well. You'll need to use javac to compile all dependent files first, then run the main class. The single-file mode is only meant for simple, self-contained programs.
  • Debugging/Inspection: Having a .class file lets you inspect the bytecode (with tools like javap) or use it in larger projects, which isn't possible with the in-memory compilation from the direct java command.

内容的提问来源于stack exchange，提问作者Nobody