Re:Show HN: Gogit – Just enough Git (in Go) to push itself t...
by tedunangst on Saturday July 29, 2023 @05:42PM
(#36924970)
I don't think you're expected to use a git client that's missing just about every wanted feature.
Re:Show HN: Gogit – Just enough Git (in Go) to push itself t...
by lopkeny12ko on Saturday July 29, 2023 @05:50PM
(#36925048)
Exactly why I find this article so confusing.
Re:Show HN: Gogit – Just enough Git (in Go) to push itself t...
by Matl on Saturday July 29, 2023 @06:02PM
(#36925145)
Why do you comment on Hacker News? After all there are many other commenters with insightful comments people presumably want to read.
If you answered; 'for fun', 'to learn something' etc. then you know why this blog post exists.
Re:Show HN: Gogit – Just enough Git (in Go) to push itself t...
by zeroxfe on Saturday July 29, 2023 @05:45PM
(#36925001)
Feels like you're missing the spirit of the article. Nobody's advocating it as a git replacement -- the author is just posting thoughts about something they built.
Re:Show HN: Gogit – Just enough Git (in Go) to push itself t...
by Chico75 on Saturday July 29, 2023 @05:48PM
(#36925030)
Nowhere does the author advocates for using its tool instead of git. Not everything is about self-promotion, sometimes it's simply knowledge sharing.
Re:Show HN: Gogit – Just enough Git (in Go) to push itself t...
by egypturnash on Saturday July 29, 2023 @05:56PM
(#36925097)
The second paragraph explains why this exists, and it's not to provide a useful implementation of Git.
> I wanted to compare what it would look like in Go, to see if it was reasonable to write small scripts in Go – quick ’n’ dirty code where performance isn’t a big deal, and stack traces are all you need for error handling.
It's a toy problem that's just big enough to be interesting. Comparing it to Hoyt's earlier Python implementation of the same problem lets him evaluate how Go would fit into a certain place in his development workflow.
Re:Show HN: Gogit – Just enough Git (in Go) to push itself t...
by patmorgan23 on Saturday July 29, 2023 @06:06PM
(#36925193)
People build things for practice all the time and then write up their experience and what they learned.
> This is going to be a short section, because I don’t care about speed in this program, and the Go version is likely as fast or faster than the Python version.
That's...fine I guess, but it is disingenuous to compare the performance of this git client to another git client written by the same author but in a different language. As a reader and someone trying to understand how and why gogit would fit into my development workflow, I don't care how it stacks up against "pygit," I care how it stacks up against git.
> Conclusion > When used with panic-based error handling, Go is good for writing quick ’n’ dirty command line scripts.
Decent conclusion for the author himself, but no one else cares--the question of "why should someone migrate to this over git?" is still painfully unanswered.