News for hackers. Stuff that matters.
Re:Brad Fitzpatrick on the future of Go by kyllo on Tuesday October 14, 2014 @02:18PM (#8454851)
Perhaps, but the problem is, with no generics or exceptions, it might just be too low-level and not expressive enough to really be a suitable Java replacement.
Re:Brad Fitzpatrick on the future of Go by agmcleod on Tuesday October 14, 2014 @02:42PM (#8454991)
Yeah i just see Go as an alternative for web technologies, where Rust is much more system level focused. I could be wrong, but that seems to be the direction I see with Rust.
Re:Brad Fitzpatrick on the future of Go by naasking on Tuesday October 14, 2014 @03:40PM (#8455295)
> Yeah i just see Go as an alternative for web technologies

I don't see any web technology Go could replace. Not even dynamically typed langauges.

Re:Brad Fitzpatrick on the future of Go by tptacek on Tuesday October 14, 2014 @04:50PM (#8455727)
We could not have handled the load at Microcorruption, emulating CPU state for thousands of concurrent users, using Ruby --- which remains the front-end language for the site.

We could easily have done so in Java, but we'd be in Java's concurrency model, which is much more difficult to reason about.

Re:Brad Fitzpatrick on the future of Go by kyllo on Tuesday October 14, 2014 @05:35PM (#8455971)
So, you did it in Go instead of Java, right?

I think this is exactly what people mean when they say Go is more of a replacement for Java than it is a replacement for C++: In the sense that when Ruby and Python become too slow, people normally reach for Java, but now they have Go as an alternative option, with a better concurrency model than Java's.

Re:Brad Fitzpatrick on the future of Go by tptacek on Tuesday October 14, 2014 @06:21PM (#8456144)
We never even considered writing it in Java. We wanted something with the performance characteristics of C, which is what we would have used had we not had Golang.
Re:Brad Fitzpatrick on the future of Go by seunosewa on Wednesday October 15, 2014 @05:50AM (#8457731)
Golang does not have the "performance xteristics of C"!
Re:Brad Fitzpatrick on the future of Go by tptacek on Wednesday October 15, 2014 @07:08PM (#8462371)
I must just be crazy.
Re:Brad Fitzpatrick on the future of Go by threeseed on Tuesday October 14, 2014 @06:56PM (#8456283)
There are alternatives to Java's concurrency model whilst still staying on the JVM:

http://docs.paralleluniverse.co/quasar/

Re:Brad Fitzpatrick on the future of Go by vec on Tuesday October 14, 2014 @04:11PM (#8455481)
I'm starting to use Go as an arguably better Node. Very fast, easy (pseudo)concurrency, relatively nice HTTP capabilities in the stdlib. It wouldn't be my first choice for building a full library, but it works well as an internal component in a service oriented architecture or a background worker for a queuing system.
Re:Brad Fitzpatrick on the future of Go by sagichmal on Tuesday October 14, 2014 @04:37PM (#8455645)
Go is very uncontroversially a better Node. It also predates Node.
Re:Brad Fitzpatrick on the future of Go by spion on Tuesday October 14, 2014 @05:01PM (#8455787)
Depends on what you mean by "better".

Better language? Not really, if you want types TypeScript is a much better option. With node+typescript+react you can get end-to-end typechecked code with no FFI involved - thats really, really cool.

Better concurrency? Oh yeah, definitely. Better core libraries? Yes, by far.

Better package ecosystem and management? Definitely not.

Re:Brad Fitzpatrick on the future of Go by sagichmal on Wednesday October 15, 2014 @02:06PM (#8460467)

    > Better language? Not really,
There is no conceivable universe in which the expression "JavaScript is a better language than Go" evaluates to true.
Re:Brad Fitzpatrick on the future of Go by spion on Friday October 17, 2014 @05:26AM (#8470093)
Unless/until Go gets generics, I stand by my statement. A horrible type system that severely limits expressiveness is worse than no type system. Even TypeScript's type system is miles ahead compared to the one in Go.
Re:Brad Fitzpatrick on the future of Go by kyllo on Thursday October 16, 2014 @07:16PM (#8468461)
...except for in JavaScript itself:

    ~$ node
    > "JavaScript is a better language than Go" ? true : false
    true
    > "JavaScript" > "Go"
    true
Re:Brad Fitzpatrick on the future of Go by general_failure on Tuesday October 14, 2014 @06:12PM (#8456106)
I doubt it. The node ecosystem is second to none.
Re:Brad Fitzpatrick on the future of Go by aikah on Wednesday October 15, 2014 @01:28AM (#8457277)
All the things node is designed to do and it does it at least as fast as Go.

We can argue that the Go concurrency model is better.I think nodejs's is good enough,easier to understand and to deploy. If your goal is to write lightweight webservers that do a specific task,nothing beats node in my opinion.

Re:Brad Fitzpatrick on the future of Go by e12e on Wednesday October 15, 2014 @04:36AM (#8457612)
> easier to ... deploy

Ehm, really? Tree of javascript, possibly with some compiled libraries easier to deploy than a static binary?

I'm not saying node is hard to deploy, but I think maybe I'm misunderstanding what you mean here?

Re:Brad Fitzpatrick on the future of Go by cft on Tuesday October 14, 2014 @04:26PM (#8455576)
Prime candidate is any highly scalable TCP socket server. Currently, there's no better language for it
Re:Brad Fitzpatrick on the future of Go by pjmlp on Tuesday October 14, 2014 @04:50PM (#8455725)
Erlang? That switch that is routing your phone calls?
Re:Brad Fitzpatrick on the future of Go by coldtea on Tuesday October 14, 2014 @10:07PM (#8456853)
It hasn't rooted anybody's phone calls for a long time. Even Ericsson doesn't use Erlang based phone routing anymore...
Re:Brad Fitzpatrick on the future of Go by kasey_junk on Tuesday October 14, 2014 @08:51PM (#8456683)
Almost certainly not TCP socket based nor built on commodity hardware.
Re:Brad Fitzpatrick on the future of Go by rdtsc on Wednesday October 15, 2014 @02:22AM (#8457373)
Erlang is a better for it. WhatsApp runs their infrastructure on it. Can easily do millions of concurrent TCP connections on a single machine.