Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Go-git – low-level and extensible Git client library in Go

github.com

Post reply on HN
Print view View original

21–30 of 60 posts

Re: Show HN: Go-git – low-level and extensible Git client library in Go

#21

Post by brudgers »

xiaq wrote: post #13
brudgers wrote: post #11

Earlier quoted context omitted.

Golang is the new Java. Google designed it for legions of corporate systems coders. It is ultimately destined to be seen as the enterprise language that it is [twenty years ago all the cool kids loved Java]. Google policy is no map function for you, it's just more palatable to bake it into the language than an HR document...it's still pure policy steeped in pointy haired logic. Don't get me wrong, it's better than it…

Golang is no more a Google language than Unix is an AT&T OS. And why are "corporate languages" necessarily bad?

On the one hand, I was responding to the Atwood's law reference. On the other hand, I have become interested in the way corporations use open-source as a strategy and implement that strategy tactically via sort of "basic fighter maneuvers" energy management discipline. [1]

Incipient potential competitors who adopt Go draw a dependency on Google because for all practical purposes, Google will determine the direction of Go: it's core team works there. And incipient potential competitors have radically different needs.

We can differ in opinion upon whether Unix was seen an ATT operating system. For me the legal and licensing histories suggests that it was in a strong sense and the "Open" and "Free" and "Li___" are the heritage.

YMMV.

[1]: https://en.wikipedia.org/wiki/Basic_fighter_maneuvers

Re: Show HN: Go-git – low-level and extensible Git client library in Go

#23

Post by woah »

hellofunk wrote: post #15
donatj wrote: post #8

Earlier quoted context omitted.

Go's lexical scoping and first class function/method's owe a lot to JS for leading the way IMHO. That said, it's "object" system is almost the complete reverse. JS is methods with data, Go is data with methods. It's an interesting contrast.

First class functions and lexical scoping have been actively used in programming languages since 4 decades prior to the invention of JS.

Mysteriously they gained popularity at the same time that JS did.

Re: Show HN: Go-git – low-level and extensible Git client library in Go

#24

Post by mwsherman »

brudgers wrote: post #11
xiaq wrote: post #5

Golang is the new JavaScript: everything that can be rewritten with it will be :)

Golang is the new Java. Google designed it for legions of corporate systems coders. It is ultimately destined to be seen as the enterprise language that it is [twenty years ago all the cool kids loved Java]. Google policy is no map function for you, it's just more palatable to bake it into the language than an HR document...it's still pure policy steeped in pointy haired logic. Don't get me wrong, it's better than it…

Maybe, in the sense that Go is designed for the use case of large teams of everyday coders (i.e., not PL enthusiasts). A similar use case to Java, no doubt.

That said, Java (and C#, which is where my experience lies) are fundamentally bureaucratic languages. Things like hierarchical namespaces and several layers of accessibility very much mirror their human-org counterparts. Explicitly implemented interfaces are a way of saying “I comply”.

Go, by contrast, is much flatter. Which, perhaps, is where organizations are heading. And interfaces are implicit, which is a way of just doing the job instead of declaring compliance.

Re: Show HN: Go-git – low-level and extensible Git client library in Go

#25

Post by mvader »

dangerlibrary wrote: post #18
icholy wrote: post #14

Earlier quoted context omitted.

> Golang is the new Java. So, a fast cross-platform runtime, simple language with good tooling, and lots of successful projects under its belt? Sounds good to me.

But with a statically-compiled executable that skirts all the problems with java classpaths and JARs and makes deploys trivial. It's almost like engineers at Google wrote a ton of Java, realized it's faults (along with being sick of paying patent ransoms to Oracle) and wrote a language that was similar but addressed the major pain points for them.

And with a remarkable and well designed standard library.

Re: Show HN: Go-git – low-level and extensible Git client library in Go

#26

Post by masklinn »

xiaq wrote: post #5

Golang is the new JavaScript: everything that can be rewritten with it will be :)

That kinda sorta makes sense given the feeling that "cgo is not go" (http://dave.cheney.net/2016/01/18/cgo-is-not-go). Without cgo no FFI, without FFI you have to reimplement whatever you need in the host language.

Re: Show HN: Go-git – low-level and extensible Git client library in Go

#27

Post by EvanPlaice »

brudgers wrote: post #21
xiaq wrote: post #13

Earlier quoted context omitted.

Golang is no more a Google language than Unix is an AT&T OS. And why are "corporate languages" necessarily bad?

On the one hand, I was responding to the Atwood's law reference. On the other hand, I have become interested in the way corporations use open-source as a strategy and implement that strategy tactically via sort of "basic fighter maneuvers" energy management discipline. [1] Incipient potential competitors who adopt Go draw a dependency on Google because for all practical purposes, Google will determine the direction o…

Go is an incremental improvement over the C++ ecosystem without all the legacy baggage.

By controling the platform, Google can leverage the ecosystem to attract and cherry-pick early adopters to the language.

Once the language becomes populat enough that the Enterprise starts to adopt it, Google will already be onto their next 'ground breaking' technology.

Once people settle on a perception they tend to hold on to it for life. One day soon people won't want to use Java. It'll be seen as "our Dad's language". Steve Yegge (ie now a Googler) said as much during his OSCON 2007 talk.

The value isn't in the language/platform, it's the people who adopt/build/use it.

Microsoft knows this, developers are what kept them afloat during a decade of stagnation in product development. Oracle thought they could buy their way in by acquiring Sun; except, while they were busy suing Google, Amazon sprinted ahead of the pack with their cloud services platform.

This is how the biggest players make long-term investments. Guarantee an abundant stream of top tier talent and success will follow.

Re: Show HN: Go-git – low-level and extensible Git client library in Go

#28

Post by mrits »

mwsherman wrote: post #24
brudgers wrote: post #11

Earlier quoted context omitted.

Golang is the new Java. Google designed it for legions of corporate systems coders. It is ultimately destined to be seen as the enterprise language that it is [twenty years ago all the cool kids loved Java]. Google policy is no map function for you, it's just more palatable to bake it into the language than an HR document...it's still pure policy steeped in pointy haired logic. Don't get me wrong, it's better than it…

Maybe, in the sense that Go is designed for the use case of large teams of everyday coders (i.e., not PL enthusiasts). A similar use case to Java, no doubt. That said, Java (and C#, which is where my experience lies) are fundamentally bureaucratic languages. Things like hierarchical namespaces and several layers of accessibility very much mirror their human-org counterparts. Explicitly implemented interfaces are a wa…

I wonder if you have taken the time to use Go. I no longer use it but I found it much more enjoyable than C++. I went back to Python for my side projects.

Re: Show HN: Go-git – low-level and extensible Git client library in Go

#30

Post by eisokant »

Gurrewe wrote: post #16

Oh, so this is how Tyba found me. Cool stuff! Is there a way to see what information sourced has about yourself?

Hi Gustav! It is, all though these days we're named source{d}. We're working on some very cool visualisations to release later this year that allow you to dig in on all of the insights we've learned from your code. Right now there is no way yet, we're completely emerged on focusing on improving our backend (and doing some very cool stuff around deep learning to analyse your code). I'll keep you posted once we release.
Post reply on HN