Can you elaborate? I can do debugging, run code and tests in VS Code.
VSC has JSON configurations for executing tasks but it's non-trivial to configure. A proper IDE would provide a graphical, fool-proof configuration for that because it's easy for non-professional to accidentally destroy your JSON file.
Also, if you have to use terminal in an IDE for trivial tasks, then it's also not an IDE.
Not that I liked GUIs, but with IDEs, like Eclipse or Visual Studio, one wouldn't have to configure something with JSONs.
VSCodium's debuggers do have point-and-click configuration.
I think your point stands, though - the easy-button debugger setup has plenty of room to improve, and the majority of the user community focuses on the JSON debugger config - so most developers using VSCodium are going to be hand-crafting JSON configs to set up their debugger.
Can you elaborate? I can do debugging, run code and tests in VS Code.
VSC has JSON configurations for executing tasks but it's non-trivial to configure. A proper IDE would provide a graphical, fool-proof configuration for that because it's easy for non-professional to accidentally destroy your JSON file.
Also, if you have to use terminal in an IDE for trivial tasks, then it's also not an IDE.
Not that I liked GUIs, but with IDEs, like Eclipse or Visual Studio, one wouldn't have to configure something with JSONs.
VSCodium's debuggers do have point-and-click configuration.
I think your point stands, though - the easy-button debugger setup has plenty of room to improve, and the majority of the user community focuses on the JSON debugger config - so most developers using VSCodium are going to be hand-crafting JSON configs to set up their debugger.