-
Notifications
You must be signed in to change notification settings - Fork 157
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
Go is called Go, not Golang #67
Comments
IMO, 'golang' is more accurate as it differentiates the module system that's built into the go language vs third-party package managers for go such as dep and glide (among others). One thing to consider is that PURL is already widely adopted in certain verticals. Changing it would inevitably break compatibility with commercial and open source tooling that already supports it. Note to the rest of the admins: this is one of the reasons why #50 is so important. |
I'm not sure about your first point. The go tool is called go, not golang: one writes 'go mod' not 'golang mod'. So golang vs. go has nothing to do with modules. Regarding compatibility, until 1.0 happens is the time to get things right. Things can change until 1.0 is settled, and this is one thing I'd like to see changed. I value your goals here in setting up a proper standard for a messy place. |
That commit does not provide an explanation but the comment above claims it is due to a mistaken belief that there is a different term for the module system than for the language. |
@robpike I am honored that you (the creator of Go) drops by and cares about this little project! The rationale for the switch from In that context, Therefore I decided then to use golang instead (and that happened in the early drafts). Since we now have a single scheme You also wrote:
I have been resisting calling a version... but it looks like pressure is piling up! @stevespringett you wrote:
I get your point but this is likely to be something that could occur again in the future, so what do you think about having aliases for
I reckon that having a settled version may be best, but at the same time I have been resisting doing so so thing could settle into place nicely. |
@ashcrow what's your take on this too? |
Switching to Alias support might be nice, but I fear we'd be trying to future proof for something that shouldn't happen often. |
@pombredanne Thank you for your careful consideration. The background is interesting. |
Since the language is called Go, even though its domain is golang.org, it would be nice (and short) if the package identifier for Go modules was "go" rather than "golang".
The text was updated successfully, but these errors were encountered: