DEV Community

Discussion on: Will Golang ever stop using their strict GOPATH path in order to code with it

Collapse
bias profile image
Tobias Nickel

didn't golang introduce go modules for this reason? I thought today you don't need thePATH anymore.

Still in my opinion it is still difficult that the entire folder can be the same package. Maybe I am just more used to the node way. but it is nice, because is absolute explicit.

Collapse
wchr profile image
Wachira Author • Edited

Yeah, it's optional. I also love the node way, simple, the only bummer is the node_modules gigabyte of packages for each node project

Collapse
bias profile image
Tobias Nickel

yes, the size is a problem, But over the years, I found no metter in what env or tech, we will always work on the limit.

Storage is cheap, and it is really powerful, to have the dependencies separate for an extra project.

I once meet a java developer, he was kind of joking, that for every project you should ship its own eclipse IDE. Because when the colleagues have different plugins, versions or config, a project often can not build.

When I was at university, they set us up in development windows VM in the cloud, so we will all have the same environment.

I am so glad not to do Java. 👍