News for hackers. Stuff that matters.
Re:Go vs. Rust: Productivity vs. Performance (2014) by pjmlp on Tuesday June 16, 2015 @06:11AM (#9724801)
> Go seems to be for the Python, Ruby and Java developers and will be used for enterprise applications, mobile apps and application servers.

No thanks, Go offers no benefit over the Java eco-system, neither in terms of deployment[0][1][2], not in terms of libraries and dependency management, nor in language expressiveness (Java 8, Scala, Clojure, Kotlin, Ceylon, Groovy)

[0] http://www.excelsiorjet.com/

[1] http://robovm.com/

[2] http://www-01.ibm.com/support/knowledgecenter/api/content/SS...

EDIT: Also forgot to add that we enterprise devs also have C#, F#, Swift, C++14, C++/CX at our disposal

Re:Go vs. Rust: Productivity vs. Performance (2014) by copx on Tuesday June 16, 2015 @07:40AM (#9725061)
[0] Price per developer (!) $3000, only supports Java 7. To compare, the price of the Go compiler per developer: $0

I see one clear benefit right there.

Re:Go vs. Rust: Productivity vs. Performance (2014) by dleskov on Wednesday June 17, 2015 @07:17AM (#9731055)
Low/zero cost is a benefit only if everything else is equal. Eclipse and Netbeans are free, yet people pay for IntelliJ IDEA. We use an expensive commercial GUI testing product because all the free and cheaper alternatives sucked big time, and support was either poor or non-existent.
Re:Go vs. Rust: Productivity vs. Performance (2014) by dleskov on Wednesday June 17, 2015 @07:37AM (#9731107)
[0] can be had at $10+ under a charity program at the moment: http://www.excelsiorjet.com/charity
Re:Go vs. Rust: Productivity vs. Performance (2014) by pjmlp on Tuesday June 16, 2015 @08:30AM (#9725229)
I just wanted to list a few examples.

Almost all commercial JVMs do support AOT compilation.

Plus we are talking about the enterprise here, those values are peanuts in project budgets.

Also don't forget to add "developer time * cost per hour" writing repetitive code in Go to your price.