Closed dmitshur closed 7 years ago
Sure, done.
That was my fault. I saw that feature appear and didn't know what it was and typed some random stuff or just clicked the suggested things.
What about the redundancy between language and programming-language?
Thanks.
What about the redundancy between language and programming-language?
That also seems like it could be improved slightly, but I haven't researched those topics and I don't mind it as much, because it's not acting as an example for other Go repositories to follow.
From a quick search, both seem to be about equally used:
You could go with just language
, since most languages on GitHub are likely programming languages anyway, and it's shorter/simpler. But I don't have a strong preference in either direction.
Background
A month ago, GitHub released a new feature called Topics.
https://github.com/blog/2309-introducing-topics
Since that time, many Go repositories on GitHub have started using a topic to indicate that the repository is primarily powered by (or related to) the Go programming language.
However, there seems to be a nearly equal split between the exact keyword(s) used:
go
as the keyword.go
topic only.go
topic only.go
topic only.go
topic only.go
topic only.go
topic only.go
topic only.golang
as the keyword.golang
topic only.golang
topic only.golang
topic only.golang
topic only.golang
only, instead ofgo
or both.)go
andgolang
, because they're not sure which one they're supposed to pick, and they don't want to "miss out".go
andgolang
topics.go
andgolang
topics.go
andgolang
topics.go
andgolang
topics.go
andgolang
topics.Given that topics are specific keywords (rather than normal words) with no spaces allowed, it seems that both
go
andgolang
are very effective at finding projects actually related to Go, the programming language.In other words, both topics are equally viable, and both topics have nearly zero false-positive matches. This is contrary to doing a normal search on a general search engine like google.com, where searching for just "golang" has much fewer false positives than searching for "go" (without additional words). Also, as I understand, the golang.org domain was out of necessity, since go.org is not a valid domain (because 2 letters is too short for a .org domain).
Issue
This issue is about the fact that the Go project repository on GitHub (https://github.com/golang/go) uses both
go
andgolang
topics, instead of justgo
:It seems unnecessary and counter-productive to be undecided, and it encourages others to be uncertain which topic to use for signaling that "this is related to the Go programming language".
Given that the language is called Go, not golang, and that
go
is a viable topic name without false positives, I believe it should be preferable.The Go project repository should remove its
golang
topic to prevent confusion and not to encourage using 2 topics for the exact same thing.Also note that GitHub detects Go language and displays it as "Go", not "golang":