4 ms·

I'm still a little confused as to why Haunts keeps getting used as an example of Go "failing". As discussed in other Go-related comment threads, the project wou

I'm still a little confused as to why Haunts keeps getting used as an example of Go "failing". As discussed in other Go-related comment threads, the project would have likely failed with any language, not just because Go doesn't have a version pinning package manager.

brown9-2 13y ago
It's confusing why anyone would seek to blame a project's failure on the choice of programming language. The presence of this anecdote in the article seems to fulfill some sort of journalistic requirement to balance any positive stories with criticism as well, to be in the center. It doesn't make a lot of sense when writing about programming languages.
- obviouslygreen 13y ago
  It's confusing why anyone would seek to blame a project's failure on the choice of programming language. The choice of language does have the potential to deep six a project; however, it's rarely something that can be blamed on the language itself. I've seen projects fail because of the language the chose for at least two reasons, but I think these two are the most obviously harmful: 1. Choosing a language that isn't just unsuitable, its design goals and tradeoffs should make it an obviously poor choice in terms of your requirements. 2. Choosing a language for use by a team that has no experience with it, no time to learn it, and/or lacks the discipline to learn it in sufficient depth to use it efficiently for the project's purposes. Again, these are not failures of any given language. They are, however, potential project-killers that are only possible based on the choice of programming language.
rubinelli 13y ago
What baffles me isn't the lack of a version pinning package manager, but that a significant portion of the Go community actively criticizes projects trying to implement them, like http://gonuts.io http://gonuts.io or https://github.com/GPMGo/gopm https://github.com/GPMGo/gopm
- codygman 13y ago
  Yeah, I saw the post about gonuts.io on the mailing list and wished the creator would have gotten a warmer welcome. Some valid points were brought up, but everyone seemed to be annoyed at him.

brown9-2 13y ago

It's confusing why anyone would seek to blame a project's failure on the choice of programming language. The presence of this anecdote in the article seems to fulfill some sort of journalistic requirement to balance any positive stories with criticism as well, to be in the center. It doesn't make a lot of sense when writing about programming languages.

obviouslygreen 13y ago
It's confusing why anyone would seek to blame a project's failure on the choice of programming language. The choice of language does have the potential to deep six a project; however, it's rarely something that can be blamed on the language itself. I've seen projects fail because of the language the chose for at least two reasons, but I think these two are the most obviously harmful: 1. Choosing a language that isn't just unsuitable, its design goals and tradeoffs should make it an obviously poor choice in terms of your requirements. 2. Choosing a language for use by a team that has no experience with it, no time to learn it, and/or lacks the discipline to learn it in sufficient depth to use it efficiently for the project's purposes. Again, these are not failures of any given language. They are, however, potential project-killers that are only possible based on the choice of programming language.

rubinelli 13y ago

What baffles me isn't the lack of a version pinning package manager, but that a significant portion of the Go community actively criticizes projects trying to implement them, like http://gonuts.io http://gonuts.io or https://github.com/GPMGo/gopm https://github.com/GPMGo/gopm

codygman 13y ago
Yeah, I saw the post about gonuts.io on the mailing list and wished the creator would have gotten a warmer welcome. Some valid points were brought up, but everyone seemed to be annoyed at him.