Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
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.
@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.
Alias support might be nice, but I fear we'd be trying to future proof for something that shouldn't happen often.