“Everyone in the industry uses it” is always the argument for some legacy tool before it’s replaced by something better. Case in point, Eclipse like you mentioned yourself.
> “Everyone in the industry uses it” is always the argument for some legacy tool before it’s replaced by something better.
I guess stability, tooling ecosystem, and ages of user/customer support info means nothing then, and being new is reason enough to scrap all your tooling and workflow?
Developers are paid to deliver features, and test-driving the latest and greatest fad gets in the way.
Before everything more important, maybe vscode should fix their auto complete. The suggestions are so bad, I'd turn it off before using it for anything serious.
Any number of complex refactoring, code upgrade refactoring, symbol search etc.? Knowing how to work with project configs (such as Spring, Micronaut, and non-java projects like Symfony etc.)?
