Those tools are for libraries/package management, pretty much all languages have them. Python=pip, Javascript=npm, Java/Kotlin=Maven/Gradle, ObjC/Swift=Cocoapods, and so on. Essentially you write a dependency file with all the packages you need, and then sync. These tools will download everything for you. So if you need 10 jar lib files, it will be done for you without you having to manually download each jar and configure it in the project settings path. They might look like BS at first, but once you learned their purpose you'll never go back to manual downloading of libs.
They really matter when you have a big project, and you don't want to reinvent the wheel if a library is already built.
Those tools are for libraries/package management, pretty much all languages have them. Python=pip, Javascript=npm, Java/Kotlin=Maven/Gradle, ObjC/Swift=Cocoapods, and so on. Essentially you write a dependency file with all the packages you need, and then sync. These tools will download everything for you. So if you need 10 jar lib files, it will be done for you without you having to manually download each jar and configure it in the project settings path. They might look like BS at first, but once you learned their purpose you'll never go back to manual downloading of libs.
They really matter when you have a big project, and you don't want to reinvent the wheel if a library is already built.
What about compiling/running. That (by itself, not accounting for libraries) should be done through the langs VLI, right?
No? Why the fuck not, that's how it USED to work, and I still need to catch up, so let me use my "cave man" methods.