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

Go After 2 Years in Production

blog.iron.io

Post reply on HN
Print view View original

11–20 of 178 posts

Re: Go After 2 Years in Production

#11

Post by untog »

illumen wrote: post #8
programminggeek wrote: post #5

Go seems to be hitting some kind of tipping point where it's going from being more of a niche thing with a small user base to something with a broader appeal. I don't think that it's because go is changing so much as the kinds of problems people are encountering writing web services that need to scale (or at least have that option). I've been comparing go to scala lately and what has really got me into go is the deve…

So you've enjoyed all the marketing and Google employee upvoting?

So you ignored the part where the OP described having actually used it in development and liking it?

Re: Go After 2 Years in Production

#12

Post by [deleted] »

illumen wrote: post #8
programminggeek wrote: post #5

Go seems to be hitting some kind of tipping point where it's going from being more of a niche thing with a small user base to something with a broader appeal. I don't think that it's because go is changing so much as the kinds of problems people are encountering writing web services that need to scale (or at least have that option). I've been comparing go to scala lately and what has really got me into go is the deve…

So you've enjoyed all the marketing and Google employee upvoting?

[deleted]

Re: Go After 2 Years in Production

#13

Post by Pxtl »

bhauer wrote: post #9
dancric wrote: post #3

As a developer on the Python stack, I would love to know when would be a good time to start using Go in serious production work. It seems to me that it solves a lot of the backend services infrastructure problems associated with interpretive languages (one of the reasons I was considering diving in Scala or other JVM languages), is relatively reliable, and has a fairly strong core library. It still seems bleeding edg…

The analogy is a little flimsy, but I'll run with it anyway: I consider Go today to be similar in some ways to Java at around the time of Java 1.1 or 1.2. Obviously, Go is modern and is in many ways better than today's Java 1.7. But I am trying to illustrate its maturity level and the trajectory that I believe it's on. If you recall the days of Java 1.1, it was already seeing a great deal of early traction. The early…

And like Java 1.2, it is still missing some critical deal-breaker features for a lot of people.

Re: Go After 2 Years in Production

#14

Post by tptacek »

illumen wrote: post #8
programminggeek wrote: post #5

Go seems to be hitting some kind of tipping point where it's going from being more of a niche thing with a small user base to something with a broader appeal. I don't think that it's because go is changing so much as the kinds of problems people are encountering writing web services that need to scale (or at least have that option). I've been comparing go to scala lately and what has really got me into go is the deve…

So you've enjoyed all the marketing and Google employee upvoting?

Comments like this never, ever improve threads.

Re: Go After 2 Years in Production

#15

Post by bitcrusher »

I can't be the only person who thinks Go is really interesting, but can't get over the 'package' hump... It's just too wonky for 'real-world' from my experience. For example, how do you create clear lines of separation with internal modules? If you want to use 'namespaces' then each namespace has to be it's own package, which then requires its own Repo that you have to 'go get'. There's unsustainable for a project of any useful size.

I must be missing something.

Re: Go After 2 Years in Production

#16

Post by bhauer »

Pxtl wrote: post #13
bhauer wrote: post #9

Earlier quoted context omitted.

The analogy is a little flimsy, but I'll run with it anyway: I consider Go today to be similar in some ways to Java at around the time of Java 1.1 or 1.2. Obviously, Go is modern and is in many ways better than today's Java 1.7. But I am trying to illustrate its maturity level and the trajectory that I believe it's on. If you recall the days of Java 1.1, it was already seeing a great deal of early traction. The early…

And like Java 1.2, it is still missing some critical deal-breaker features for a lot of people.

Exactly. The maturity level is about the same--obviously in different ways--but I think you get what I mean.

Will they ever add generics? Not sure. Will Java ever have proper first-class functions? Not sure.

Re: Go After 2 Years in Production

#17

Post by weego »

untog wrote: post #11
illumen wrote: post #8

Earlier quoted context omitted.

So you've enjoyed all the marketing and Google employee upvoting?

So you ignored the part where the OP described having actually used it in development and liking it?

I think we need more than 1 account of Go in production before we start high-fiving each other about Go in the mainstream.

And to be fair to the person you are responding too, there has been an inordinate amount of Go articles on HN over the last few months compared to anywhere else on the internet tech/dev wise, so much so that a number of my friends have independently made a joke of it.

Re: Go After 2 Years in Production

#18

Post by thezilch »

illumen wrote: post #8
programminggeek wrote: post #5

Go seems to be hitting some kind of tipping point where it's going from being more of a niche thing with a small user base to something with a broader appeal. I don't think that it's because go is changing so much as the kinds of problems people are encountering writing web services that need to scale (or at least have that option). I've been comparing go to scala lately and what has really got me into go is the deve…

So you've enjoyed all the marketing and Google employee upvoting?

As much as you've enjoyed the "GENERICS OR BUST" and anti-Google, downvoting crowds.

Re: Go After 2 Years in Production

#19

Post by weego »

tptacek wrote: post #14
illumen wrote: post #8

Earlier quoted context omitted.

So you've enjoyed all the marketing and Google employee upvoting?

Comments like this never, ever improve threads.

The other thing that never improves threads is everyone only posting what they think might get upvoted instead of saying what they actually think, especially when there might be a grain of truth in it. Tedious comment back-patting is the death of good communities.

Re: Go After 2 Years in Production

#20

Post by thezilch »

weego wrote: post #17
untog wrote: post #11

Earlier quoted context omitted.

So you ignored the part where the OP described having actually used it in development and liking it?

I think we need more than 1 account of Go in production before we start high-fiving each other about Go in the mainstream. And to be fair to the person you are responding too, there has been an inordinate amount of Go articles on HN over the last few months compared to anywhere else on the internet tech/dev wise, so much so that a number of my friends have independently made a joke of it.

There are plenty accounts of Go in production: (Google's dl.google.com) https://groups.google.com/d/msg/golang-nuts/BNUNbKSypE0/E4qS..., (CloudFlare's Railgun) http://blog.cloudflare.com/go-at-cloudflare, (Bit.ly) http://word.bitly.com/post/29550171827/go-go-gadget, (SoundCloud) http://backstage.soundcloud.com/2012/07/go-at-soundcloud/, (Disqus's realtime-backend) http://blog.disqus.com/post/51155103801/trying-out-this-go-t..., etc
Post reply on HN