The Java/ Kotlin editing experience on VS Code is pretty bare-bones. Unacceptably bare bones IMHO. But each tot their own.

Although, I'd be probably be pretty harsh reviewing any PRs where because of the lousy tooling the code is full of unaddressed warnings, misorganized imports, or where the author can't be bothered to refactor because they lack the tools.

The reality is that on most projects you can use whatever you want as long as it does the job, properly. VS Code is mostly not very practical on such projects for Java projects because standards tend to be pretty high because of the tooling.

VS Code is still valid of course for those who only occasionally need to do any changes. I tend to use it for things like javascript/typescript and rust or other things I use less frequently. I switched to pycharm for python though because it seems marginally better at supporting that.