If you would stop complaining if the IDE shipped with the compiler, then just install them at the same time and consider it "shipped with". Splitting them is for convenience and choice, not because the designers are stupid. You can handle installing two things.

(And since we're on the subject of Java, let's not forget how they used to split up JRE and JDK downloads in a very similar way.)

Having the IDE ready to go takes care of the use case of changing one variable, but you didn't need the IDE in the first place. That one's fine either way.

For the use case of making a whole new program in nano, I acknowledge and reject it. You'll be fine. Use cases that exist only out of stubbornness don't need to be catered to. You have the IDE one click away.

> use cases like "let me write a small program in nano over SSH" or "let me change one hardcoded variable and recompile the project and never touch its source code again".

1. This is an infinitesimally small use case

2. Often those same programmers somehow are completely fine using C++ or Rust

3. Even more often those same programmers deny the usefulness of IDEs just because they need those use cases once every 10 years or so, and keep using subpar tools

While I don’t agree, I do think there’s merit to the arguments you made (edit remotely, change a line and forget about it). Many anti-IDE arguments boil down to “I like a particular workflow and want to generalize it to all contexts” which is weak (you made the choice, you do the work to integrate e.g. Maven dependency awareness with your hyper customized vim environment or whatever).

However, I don’t think your arguments are sufficient to outweigh the benefits that can be obtained by making a language platform with features that assume the presence of IDE support.

Either way, I’m just one person, so you do you.