News for hackers. Stuff that matters.
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?