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

Six years of Go

blog.golang.org

Post reply on HN
Print view View original

221–230 of 327 posts

Re: Six years of Go

#221

Post by pjmlp »

donatj wrote: post #152
coldtea wrote: post #102

Earlier quoted context omitted.

> It was early 2013, when we adopted Go as a default language for all our server side (micro or not) services. (...) The reason for the move were few: 1) Ambivalence on Java roadmap So, because there was some "ambivalence for the Java roadmap", a language with multiple implementations, a huge community (including open source), and so entrenched in the industry that will be there in 2100 too, you switched to a 3-4 yea…

If Java is still around in 2100 I weep for how little progress was made.

Cobol, Fortran and Lisp are still around.

Re: Six years of Go

#222

Post by nicksardo »

lobster_johnson wrote: post #205
codemac wrote: post #195

Earlier quoted context omitted.

> particularly high-performance small services that do things like fling JSON around :/ Their json system reflects and allocates like a mad-man. It's probably one of the slowest parts of the std library.

Do you know of a faster JSON library? I've been struggling with this. My particular use case is that I don't want any fancy struct unmarshaling; I just want the equivalent of map[string]interface{}.

https://github.com/nicksardo/jsonpath can pull out parts of a JSON document without unmarshalling.

Re: Six years of Go

#223

Post by tptacek »

pvg wrote: post #216
tptacek wrote: post #141

Earlier quoted context omitted.

If everyone thought this way, our realistic professional choices of languages would be C, C++, and Perl. The exact same things you're saying about Go were things people said about Java --- a language, by the way, with much more harrowing ownership issues than Go, which is an open-source project top-to-bottom.

What do you feel are the much more harrowing ownership issues? If you google 'goroutine leaking' you get a pile of convoluted stuff. I don't mean to language-war, if anything I find 'stuff proponents and detractors said about Java in its early days' eerily similar (and likely as overwrought) to the same said about Go now.

Google is locked in a multi-billion-dollar lawsuit over the ownership of trivial bits of Java code!

Re: Six years of Go

#224

Post by threeseed »

drumdance wrote: post #135
coldtea wrote: post #102

Earlier quoted context omitted.

> It was early 2013, when we adopted Go as a default language for all our server side (micro or not) services. (...) The reason for the move were few: 1) Ambivalence on Java roadmap So, because there was some "ambivalence for the Java roadmap", a language with multiple implementations, a huge community (including open source), and so entrenched in the industry that will be there in 2100 too, you switched to a 3-4 yea…

Ha. I built my first company on Java back in 1996. It was a terrible decision. Very buggy, lots of BS from Sun & Oracle that was really more about Ellison and McNealy envying Bill Gates. Netscape made a similarly bad decision when they tried to create a pure Java version of the browser. I'm sure Java is 10x better now, but I'm not convinced it will be here in 2100.

What ? Of all the languages Java is the most likeliest to be around in 2100.

It is the lingua de franca of enterprise software development. In every sense it is the modern day Fortran/Cobol.

Re: Six years of Go

#225

Post by pvg »

tptacek wrote: post #223
pvg wrote: post #216

Earlier quoted context omitted.

What do you feel are the much more harrowing ownership issues? If you google 'goroutine leaking' you get a pile of convoluted stuff. I don't mean to language-war, if anything I find 'stuff proponents and detractors said about Java in its early days' eerily similar (and likely as overwrought) to the same said about Go now.

Google is locked in a multi-billion-dollar lawsuit over the ownership of trivial bits of Java code!

Hah, I completely misread 'ownership'!

Re: Six years of Go

#226

Post by SeanDav »

geodel wrote: post #208
coldtea wrote: post #132

Earlier quoted context omitted.

Well, still not a handful of people, but a huge endeavour, and with a published roadmap for 2 versions ahead. Besides even if Larry said "kill it" tomorrow, Java would still survive -- so much that it's used in all kinds of enterprises.

I think even if Larry said "kill it" Go will also survive :-)

On the other had, Google could kill Go tomorrow...

Re: Six years of Go

#229

Post by dang »

hahainternet wrote: post #33
chrshawkes wrote: post #32

Earlier quoted context omitted.

Go brings some good things to the table, yes. I've seen it's popularity rise in recent years, but it seems to be rising slowly. There are a ton of companies that can be listed for almost every technology. Node is another technology I would put ahead of Go as far as adoption. Maybe Go will get better, to me, it's too different than a lot of what I see day to day with Java, C#, Python, JavaScript and on and on. The par…

> Go brings some good things to the table, yes. I've seen it's popularity rise in recent years, but it seems to be rising slowly. There are a ton of companies that can be listed for almost every technology. Then name any company using Swift to the level Dropbox uses Go, or retract your claim. Go code looks nothing like C other than general brace styling. I can't decide if you're trolling or just genuinely this ignora…

> What the heck are you talking about

> I can't decide if you're trolling or just genuinely this ignorant.

Stuff like this breaks the HN guidelines. Please edit it out of your comments when posting here.

https://news.ycombinator.com/newsguidelines.html

https://news.ycombinator.com/newswelcome.html

Re: Six years of Go

#230

Post by lobster_johnson »

nicksardo wrote: post #222
lobster_johnson wrote: post #205

Earlier quoted context omitted.

Do you know of a faster JSON library? I've been struggling with this. My particular use case is that I don't want any fancy struct unmarshaling; I just want the equivalent of map[string]interface{}.

https://github.com/nicksardo/jsonpath can pull out parts of a JSON document without unmarshalling.

That's really neat, thanks (do you have any benchmarks comparing it to Go's JSON?), but doesn't cover my use case. I want all the values in a map-like API. I don't know anything about the shape of the contents, names of the keys, etc.
Post reply on HN