2 ms·
>The Go language and the Rust language. What they have in common, though, is that both Go and Rust are entirely incapable of walking like a duck. Since you cann
by pretoriusB 14y ago
>The Go language and the Rust language. What they have in common, though, is that both Go and Rust are entirely incapable of walking like a duck. Since you cannot call Rust -or Go code from a scripting engine, they are inadvertently positioning themselves as alternatives to the scripting engines themselves.
Before writing all these BS, maybe he should do a little research first?
Here's Rust (which is not even released yet) being capable of being called from C. It's a feature they are actively work on:
https://github.com/mozilla/rust/issues/1732 https://github.com/mozilla/rust/issues/1732
- bluehex 14y ago> Before writing all these BS, maybe he should do a little research first? There's a subtle difference between being able to call back into Go/Rust code from C (where the main function is in Go/Rust) which both languages allow now, and allowing a call to originate from a C program, which neither currently do. The author is talking about the later. I would agree the article could go into more detail about what's currently possible, and why it's not enough. But calling BS, I think, is going a bit too far.
- pretoriusB 14y ago>and allowing a call to originate from a C program, which neither currently do. That one is also under consideration by the Rust developers.