3 ms·
That doesn't resolve the question. It's a very odd combination of languages to decide to sling together arbitrarily.
by monadic2 6y ago
That doesn't resolve the question. It's a very odd combination of languages to decide to sling together arbitrarily.
- detaro 6y agoTwo statically compiled languages that get a lot of attention for writing tools in doesn't seem that odd choice to compare?
- monadic2 6y agoI mean you can statically compile a lot of languages and literally every language is used to write tools. Go doesn't even use a stack compatible with the system abi and has probably the worst FFI of any language I've ever used, it has a very, err, unique type system. I mean there's a shit ton of great stuff too (compile times, great test patterns and pretty good tooling, the http stack and string manipulation and green threading is fantastic), I don't have it out for go! Meanwhile rust has a completely different memory model and type system and concurrency model, has probably the best FFI of any language outside of maybe some lisps and cpython and probably D (never used it), and they've taken forever to role out production ready http client/server stacks (though I think this is finally smoothing out!) I just don't see why they're tied together except a) static compilation and b) they emerged at roughly the same time. Rust and go are very, very different languages aimed at completely different niches.