News for hackers. Stuff that matters.
Re:On Go by coldtea on Sunday June 02, 2013 @07:41AM (#5808138)
Yes, but in return they get something more mature than PyPy, something with less hassle that bringing along a VM (JVM/.NET), and something less alien and marginal than FP languages with native compilers.

They might not get the best technical experience, but they DO get:

1) mostly imperative (and most LIKE it that way), 2) nice concurrency support, 3) a lot of niceties (first class functions, implicit interfaces, maps, etc), 4) quite full batteries included, 5) lots of other kids using it 6) regular success posts on HN 7) nice, and mostly predictable, reasoning about speed and memory

Re:On Go by pjmlp on Sunday June 02, 2013 @04:38PM (#5809998)
> Yes, but in return they get something more mature than PyPy, something with less hassle that bringing along a VM (JVM/.NET), and something less alien and marginal than FP languages with native compilers.

There are commercial native compilers for Java and .NET if you are willing to pay for them. Language != Implementation

As for what one gets,

1) Offered by C++, JVM, .NET languages, D, Rust, ...

2) Scala, Haskell, OCaml, F#, D, Rust, Erlang, ....

3) Almost any modern language with exception of C and Java.

4) Java and .NET have more batteries

5) Yes, because big boys have better tools

6) Fortune 500 companies don't use languages based on HN posts

7) Tooling still behind what big boys use for other languages

Re:On Go by coldtea on Sunday June 02, 2013 @07:35PM (#5810534)
>There are commercial native compilers for Java and .NET if you are willing to pay for them. Language != Implementation

For C or C++ and a few others, maybe. For most other languages, language and implementation are very much tied, for practical reasons (size of community, maturity, degree of compatibility, etc etc).

As for using some Java/.NET "commercial native compiler" is not a real (or desired) option for most people/companies. For one, it delves into non standard waters, and can bring obscure bugs, restrictions (e.g reflection related), etc. Second, you have to pay. Third, it's one more thing to pile on top of your language choice. Where my argument was that Go gives some people using it LESS things to worry about.

For the rest of your list: the point was that they get ALL of them from Go at the same time. Being able to get one or another feature from this or that language is not comparable to that.

I also don't understand why you bring Rust into this. Rust is not production ready -- even the project leaders advise AGAINST using it for anything production related. It's also in flux, and the syntax is still changing. So, nice language as it shapes to be, isn't it obvious that it's not in any way an alternative to Go for at least one more year?

Re:On Go by pjmlp on Monday June 03, 2013 @04:02AM (#5811962)
> For the rest of your list: the point was that they get ALL of them from Go at the same time. Being able to get one or another feature from this or that language is not comparable to that.

I just wanted to enumerate a few languages where those features are present.

If you feel like, I can present an extensive list of every Go feature and which languages offer similar support.

But what would be the point besides fueling a flamewar?

I jumped into Go at the begging, because I was looking for something with the features of today's mainstream languages and the language's Oberon influence interested me. Given the time I spent with Native Oberon back in the 90's.

In the end I became disappointed as the language is not much more than Limbo (1995) reborn.

> I also don't understand why you bring Rust into this. Rust is not production ready

So what, Go also wasn't when I was using it, and it did not prevent companies like Canonical to use the language in production.

I just get the feeling if Go authors weren't working at Google, the language wouldn't be given front page presence on HN every day, given its design.

On the other hand, I wish Go becomes success as it might help decrease even more the use cases where C is still relevant.

Re:On Go by coldtea on Monday June 03, 2013 @07:04AM (#5812510)
>So what, Go also wasn't when I was using it, and it did not prevent companies like Canonical to use the language in production.

Go was far more production ready even when it first appeared (after internal development). For Rust, we are at the stage or internal development at this point, only it happens publicly. So the two are in no way comparable in that respect -- and that's why Canonical had no problem using it in production.

>I just get the feeling if Go authors weren't working at Google, the language wouldn't be given front page presence on HN every day, given its design.

Yes, but they are and so it is. Which reminds of a Jimmy Carr joke, about his girlfriend.

"People would say to me: she's only with you cause you're famous. And I'd tell them, well, I AM famous, so what's your point?".

So, even if people are using Go because of Google, well, it IS Google that is behind the language, so this also helps it.

Re:On Go by MetaCosm on Sunday June 02, 2013 @05:16PM (#5810137)
You kinda made his point for him didn't you? He said all these are benefits of Go, and you pointed out he would need to use lots of different languages to get them elsewhere.

Notice the lack of overlap in your own points(1-4), that right there is the crux of the issue. Beyond that, on (5) I simply respond... what? I think you are flat out wrong about (6) and how they pick languages (I contract for them), they "hear" node.js is super fast and will double output and want to use it. (7) is part of what Go was designed to enable, building tools for it is AWESOME (Go AST!).

If anything you made a killer post, maybe just not for the reasons you think.

Re:On Go by pjmlp on Sunday June 02, 2013 @05:50PM (#5810246)
> You kinda made his point for him didn't you? He said all these are benefits of Go, and you pointed out he would need to use lots of different languages to get them elsewhere.

Not really, I just found out it was easier to reply to his bullet points like that using languages that are known for certain features.

Actually most of those languages cover all Go features.

Anyone with background in compiler design can easily provide a paper like article that picks up every single feature and describes which languages offered them initially and their evolution across programming languages.

However something like that would only contribute for flame war discussions without any productive result.

I also work for Fortune 500 companies with multi-site offshoring projects, so I do have some experience on that world.

I was attracted to Go, because it is a Google language, but I got disappointed with its features, after using the language during 2010-11 timeframe.

It remains to be seen how the language will evolve in the marketplace, but would HN care if it wasn't a Google language?