-
Notifications
You must be signed in to change notification settings - Fork 17.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
proposal: Why GO decide to have internal dependency manager? #29161
Comments
Go get DOES use git under the hood though, doesn't it? Correct me if I'm wrong. Also, removing it would be a huge breaking change so I don't think it'll be happening anytime soon (if ever), and I'm pretty sure the devs won't be happy to scrap their work. |
1- Not always use git under the hood. you must read very carefully and deeply "Dependency Management" & "Version Control" before any misunderstanding from my proposal. |
Hi @OmidHekayati, This appears to be more a discussion/question rather than a specific Go bug. We do not use the issue tracker for general discussions or questions like these. The Github bug tracker is only used for tracking bugs and proposals going through the Proposal Process. Deprecating the entirety of go get, modules and GOPATH will be a drastic change at this point of the language. If you are proposing to replace all of this with just git, you should also propose how should we replace all of the I will close this issue since this is not the right place to discuss this. But please do feel free to continue this discussion across various forums mentioned in the Questions wiki page; it has a list of good places for asking questions. Thank you. |
1- My issue is not discussion||question. It is a real proposal to stop do the wrong thing in go! |
It is not a proposal because it does not lay out the solutions very clearly. Your issue itself questions some basic things, and just suggests git as the solution. Closing the issue does not mean it is not up for discussion. I apologize if that was the message. It is just that this issue tracker is not the right place for open-ended discussions like these. Please do feel free to ask this in golang-nuts/golang-dev to gauge what other people say. That is the right place. |
1- I think it is obvious that I suggest using any version control that you use for your project for dependency management too. Proposal||Idea always start with a why question and give a solution! 2- Ok. But I don't have enough time to discuss more for this idea. I hope someone stops these unneeded features from Golang like other good languages like C, Erlang,... . |
It is very surprising for me each programming language wants dedicated "Dependency Management" like go get, NPM, PIP, ... when this is the feature of every version control services like Git. I can't find any feature in these services that version controls can't do them!
When in any engineered software project we need a type of version control like Git and Almost all of them have internal "Dependency Management" features like "Git submodule" why you decide to add a nonstandard and annoying way to manage dependencies outside of project version control? And even worse consume technical person resources to continue to develop other related ideas.
I suggest deprecating all related to go get, GOPATH, go modules and remote import paths. And suggest every one always use a good version control for any project even tiny one! In this way, Developers can take time to learn their version control deeply and go community can work on other good ideas!
The text was updated successfully, but these errors were encountered: