Live data from Hacker News

Go After 2 Years in Production

blog.iron.io

141–150 of 178 posts

Re: Go After 2 Years in Production

#141

Earlier quoted context omitted.

The Go team at Google consists of a handful of people: http://thechangelog.com/100/

Please, let's not have an argument over which dev team is smarter. The fact is that Go and Rust are very different languages with different goals and feature sets, with different levels of ambitiousness and which started development in earnest at different times.

Agreed. There is room in this world for both projects to succeed, and I hope they do.

Re: Go After 2 Years in Production

#142
post #32

Another Scala user here. And I've been using Scala for the last six months. Mostly developing web applications on Scalatra and Play. I love Scala - It still has its goodiness and it's an excellent alternative to Java. If you notice in all of the Scala books (I've read the one by Martin and the One by David Pollak as well), they all seem to push you towards the functional programming model instead of the much more com…

I've historically been pretty pro-Scala 'round these parts, so my response to this should be considered in that light. So, with that disclosure out of the way... =) I have to admit, I don't agree with the assertion that the cognitive dissonance associated with programming in an imperative way versus a functional way is a major problem to Scala. I realize personal preference is a very big part of this, but there are m…

Maybe you would try nimrod language, it's similar to go but a bit more functional, and it has generics and the concurrence is managed using actors (also supports channel's) , and rust also is a good language for functional programmers trying to find a good system language...

Go language is so different to scala or Haskell because it follow the principle what a simple language is better than a complex one (the less powerful principle). The type system is a bit weak in go, probably one simplest type system ever, nimrod has a basic oop joining with algebraic data types and something similar to clojure multi methods, rust I believe has type classes..... So yes, I if you're happy writing functional code and using powerful languages maybe you will not totally happy with go language...

Re: Go After 2 Years in Production

#144

Earlier quoted context omitted.

I've historically been pretty pro-Scala 'round these parts, so my response to this should be considered in that light. So, with that disclosure out of the way... =) I have to admit, I don't agree with the assertion that the cognitive dissonance associated with programming in an imperative way versus a functional way is a major problem to Scala. I realize personal preference is a very big part of this, but there are m…

Maybe you would try nimrod language, it's similar to go but a bit more functional, and it has generics and the concurrence is managed using actors (also supports channel's) , and rust also is a good language for functional programmers trying to find a good system language... Go language is so different to scala or Haskell because it follow the principle what a simple language is better than a complex one (the less po…

I'll have to look at Nimrod. You're correct about Rust; I've only read bits and pieces, but everything I've seen so far has left me with a positive impression.

Re: Go After 2 Years in Production

#145
post #105
post #22

Earlier quoted context omitted.

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

3. Profit

Have you paid for your annual Go compiler license subscription yet? Yeah, me neither.

Re: Go After 2 Years in Production

#146

Earlier quoted context omitted.

It's not quite that bad in Go, (-b + math.Sqrt(b b - 4 a c)) / (2 a) though if you're using a ton of matrices it could be. I for one have found Go great for computing. The really quick compile times with static checking plus the composability are great. It definitely depends though; while the native concurrency is great there aren't a lot of easy solutions for non-shared memory computations. (I saw an MPI package at…

Sorry, new to posting on HN. How do I get asterisk literals?

Leave a whitespace after the asterisk: 1 * 2 * 3 = 6

https://news.ycombinator.com/formatdoc

Re: Go After 2 Years in Production

#147
post #17
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.

HN and /r/programming both have waves of fetishes. Before Go, it was Node. Before Node, Haskell. Before Haskell, Common Lisp.

Re: Go After 2 Years in Production

#148
post #10

I know it's cliche, but I still can't live without generics or a macro-like approximation thereof. I suffered under Java 2 for too long to go back to that.

It's not cliche, it's just personal. For instance, most of the code I write is numerical code. To that end, any language without operator overloading is a non-starter, since it's far harder to find a bug in: div(add(mult(-1,b),sqrt(sub(pow(b,2),mult(mult(3,a),c)))),mult(2,a)) than it is in (-b+sqrt(b^2-3 a c))/(2*a) On the other hand, if I wrote server code, operator overloading would be far less useful. I'd probably…

You and FORTRAN were made for each other.

Re: Go After 2 Years in Production

#149
post #85
post #74

Earlier quoted context omitted.

If you are talking about a breakdown of time consumed during a single request's processing, then yes on slower platforms/languages/frameworks, the database access portion may not be the most significant percentage of time used. But this is not that relevant as even the slower platforms usually can handle a single request reasonably fast. What I was talking about was more about in the scaling of a system, i.e. what ha…

"Reasonably fast" is in the eye of the beholder. In my opinion, many popular platforms and frameworks are not reasonably fast at providing a response in real-world applications. As a result, many web sites are frustratingly slow in my opinion (for example, a popular site used for hosting source code repositories). If those sites were to capture and share their profiling data (including time spent in drivers and the O…

I think the confusion arises because jd007 is discussing throughput and you are discussing latency.

Latency and throughput can be inversely related depending the precise architecture of a system (queueing is the classic mechanism that trades them off).

But in terms of "horizontal scaling", the goal really is to improve total throughput. Often imposing a tax on latency due to coordination costs.

Re: Go After 2 Years in Production

#150

Earlier quoted context omitted.

Well, then write for me a type-agnostic map function that does not rely on introspection.

If you understood how to write Go, you would write an imperative ad-hoc loop instead of composing generic functional combinators. But you have to be mature enough to jump over the shadow of your functional pride and write clean imperative code.

Loops impose order. Maps do not.

Maps are in principle trivial to parallelise. That would be a nice feature.

Post reply on HN