3 ms·
> go isn't ready at all It's ready when people use it in production.And that's the case so it's ready. > it does have some marquee names behind it, So does
by aikah 12y ago
> go isn't ready at all
It's ready when people use it in production.And that's the case so it's ready.
> it does have some marquee names behind it,
So does Rust,or are you saying Mozilla isn't a strong brand?
I don't think its fair to compare both anyway.
Rust looks like it wants to compete with C++, while Go is used by scripters coming from Ruby,Python,Js and PHP. Go devs aren't interested in memory unsafe programming.
- adamnemecek 12y agoyou skipped the "if you're interested in rust's memory safety, performance, low-level control, and expressive type system, then in a very real way" part.
- aikah 12y ago> you skipped the "if you're interested in rust's memory safety, performance, low-level control, and expressive type system, then in a very real way" part. You skipped the fact that user oldmanjay heavily edited his message, and the current one has little to do with the one I answered too. Not going to edited mine, I quoted his previous message and answered to these specific points.
- dbaupp 12y ago"go isn't ready at all" is still a substring of the parent comment, so one perfectly valid interpretation is that the quote was taken out of context, especially since HN provides no edit histories or even indication of edits.
- aikah 12y ago> you skipped the "if you're interested in rust's memory safety, performance, low-level control, and expressive type system, then in a very real way" part. Was not part of the original comment I answered to.