Comparing Rust to Go is equally unproductive, given that they target wildly different use cases and embody dramatically different philosophies. You might as well compare Lua to Objective-C, or OCaml to Malebolge.
Re:Summary of Golang Generics Discussion
by codygman on Tuesday December 16, 2014 @09:58AM
(#8757378)
What advantages does Go have over Erlang?
Re:Summary of Golang Generics Discussion
by sacado2 on Tuesday December 23, 2014 @09:34AM
(#8788220)
It can be learned by a programmer knowing only imperative C-family languages in a couple of hours, meaning I can hire any average developer and make him productive in less than a week. Not the same as teaching pure functional style with pattern-matching and prolog's syntax. Go is also much more efficient. It also produces static executables and can be easier to deploy -- or not, depending on the exact situation. It handles strings nicely -- anything other than Erlang's approach to strings is nice.
Erlang has other advantages, though. 99.9999999% uptime and hot code replacement are easier with it, for instance. Their ideal niches don't completely overlap.
Re:Summary of Golang Generics Discussion
by codygman on Tuesday December 23, 2014 @02:54PM
(#8789873)
I believe I can agree to the above statements.
Re:Summary of Golang Generics Discussion
by commentzorro on Tuesday December 16, 2014 @10:09AM
(#8757434)
What advantages does Erlang have over Factor?
Re:Summary of Golang Generics Discussion
by codygman on Tuesday December 16, 2014 @06:49PM
(#8760309)
I don't know much about Factor, it's a Forth implementation right? Just inspired by Forth?
Either way, the example[0] I was greeted with on the homepage[1] is quite awesome. Does it have an actor implementation like Erlang? How does it handle concurrency?
0:
USING: io kernel sequences
http.client xml xml.data xml.traversal ;
"http://factorcode.org" http-get nip string>xml
"a" deep-tags-named
[ "href" attr ] map
[ print ] each
1: http://factorcode.org/
I have been writing Go code professionally nearly every day for 6 months. Would I rather be writing C? Probably. Python? Not on a project of this scale. C++? Toss up. Java? No - doing far to much interfacing to C libs for that. Rust? Probably. Go is far from perfect, but honestly not that bad.