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

21–30 of 178 posts

Re: Go After 2 Years in Production

#21

Post by melling »

programminggeek wrote: post #6
melling wrote: post #2

The memory footprint for Go seems to makes it ideal for mobile devices. Also, considering that Dalvik performance is much slower than Java, it really seems like have Go on Android would be a huge win. http://en.wikipedia.org/wiki/Dalvik_(software)#Performance Go compiles to native, so "compile on install", would probably be needed.

Go on Android would be great, but Google used Java in the first place so that they could leverage all the Java devs in the world to build Android apps. Go might be a much better choice from a pure dev standpoint, but from a getting everyone to build apps standpoint, it's a fail in the short/middle term.

I didn't say get everyone to build apps. It would simply be another option. App development is getting more competitive, of course, so people that want to stand out might need to move to Go to gain an edge. Plus, I image that a Go environment might provide a better interactive development cycle.

Re: Go After 2 Years in Production

#22

Post by _ak »

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?

Yes, it's all a conspiracy! Because that's how open source development at Google work: create shitty technology, spam HN, Reddit et al. with it, and then let the massive Google workforce and the fanboys upvote the postings.

/s

Re: Go After 2 Years in Production

#23

Post by swah »

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…

Their philosophies are so different, though. Mostly the only thing they have in common is being "modern" in their own ways.

Re: Go After 2 Years in Production

#24

Post by voidlogic »

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.

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

I've been programming in Go full time since Go 1.0. Lots of companies use Go: http://golang.cat-v.org/organizations-using-go -And that is list out of date and not maintained. For example, companies like Mozilla and Walmart are not on that out of date list.

Re: Go After 2 Years in Production

#25

Post by _ak »

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.

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

http://code.google.com/p/go-wiki/wiki/GoUsers

http://code.google.com/p/go-wiki/wiki/SuccessStories

Just sayin'.

Re: Go After 2 Years in Production

#26

Post by BarkMore »

bitcrusher wrote: post #15

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…

Organize your packages in a directory tree. You can check the entire tree into a single repository. There's no requirement to put the code in a repository or use 'go get'.

The page at http://golang.org/doc/code.html explains how to organize code into packages.

Re: Go After 2 Years in Production

#27

Post by gruseom »

weego wrote: post #19
tptacek wrote: post #14

Earlier quoted context omitted.

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.

How about we avoid both trollish sarcasm and tedious back-patting, and say what we really think politely? That's not so hard.

Re: Go After 2 Years in Production

#28

Post by Game_Ender »

bitcrusher wrote: post #15

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…

Google has said they don't use 'go get' internally to manage dependencies, so they appear to agree with you.

Re: Go After 2 Years in Production

#29

Post by trevordixon »

bitcrusher wrote: post #15

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…

Exactly what I've been wondering. I've done `import "./[internal_module]" in some of my little experiments, but I've read that's unacceptable.

Re: Go After 2 Years in Production

#30

Post by eranation »

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…

Oh, painful point, I still try to ignore Scala's compile time and hope it will improve in the future, (it does gradually on every release) but when I do, then Scala feels a bit more natural to me than Go (it feels closer to Ruby for me, which I like, and has the Java interop aspect, which I unfortunately need). I just close my eyes, do sbt ~test-quick, and hope for the best. It's just that Scala feels to me more like a statically typed Ruby, where in Go I need to shift some paradigms and do some mental twists to accept how great it is.
Post reply on HN