3 ms·

Well, and I mean this kinda snarkily, who said people don't? I, for one, found that for some kinds of work I do, Go doesn't give that much of a performance adv

by batista 14y ago

Well, and I mean this kinda snarkily, who said people don't? I, for one, found that for some kinds of work I do, Go doesn't give that much of a performance advantage, so I'm exploring other languages. That said, even if Java gives you 2x, that doesn't mean that you shouldn't complain about Go. E.g you might like Go's semantics and syntax, or it might have other benefits for you. That you like those things about Go, doesn't mean you don't get to say "shame about the performance".

tptacek 14y ago
I guess I'm just saying, Go's syntax and semantics aren't enough of a win for you to deal with the performance hit you take compared to Java. So use Java. It's not a moral issue.
- wonderzombie 14y ago
  Isn't this purely subjective, especially re: semantics? It's a lot harder to measure the value of simplicity, but I'd argue that it has implications for the lifetime of your program well beyond benchmarks. It seems shortsighted to trade-off on performance alone. Would Java have been so widely adopted in the first place had that been the prevailing attitude?
- batista 14y ago
  Well, I hoped to use Go to avoid both: a) writing in C for performance (and having to setup glib et al to make it comfortable) and: b) carrying the JVM with me to run something. (And, no, I won't consider AOT compilers for Java. I want to deal with reasonably mature and widespread technologies and tooling). So, there are my constraints. Given those, maybe C++ is the ticket. D is not mainstream enough, and Rust I've played with and I like very much but is still in flux.
  - tptacek 14y ago
    I wrote three paragraphs of response here, as is my wont, and realized before hitting "reply" that that's the wrong tack. Let's be specific. What are you building or considering, where your current options are C and the JVM? How does Go fall down on that work load? I've got a fair bit of professional experience in both C (~10 years shipping code continuously in it) and Java, and I've spent the last couple weeks in Go --- not long enough to be a true believer, but enough to have some practical experience.

by batista 14y ago

tptacek 14y ago

I guess I'm just saying, Go's syntax and semantics aren't enough of a win for you to deal with the performance hit you take compared to Java. So use Java. It's not a moral issue.

wonderzombie 14y ago
Isn't this purely subjective, especially re: semantics? It's a lot harder to measure the value of simplicity, but I'd argue that it has implications for the lifetime of your program well beyond benchmarks. It seems shortsighted to trade-off on performance alone. Would Java have been so widely adopted in the first place had that been the prevailing attitude?
batista 14y ago
Well, I hoped to use Go to avoid both: a) writing in C for performance (and having to setup glib et al to make it comfortable) and: b) carrying the JVM with me to run something. (And, no, I won't consider AOT compilers for Java. I want to deal with reasonably mature and widespread technologies and tooling). So, there are my constraints. Given those, maybe C++ is the ticket. D is not mainstream enough, and Rust I've played with and I like very much but is still in flux.
- tptacek 14y ago
  I wrote three paragraphs of response here, as is my wont, and realized before hitting "reply" that that's the wrong tack. Let's be specific. What are you building or considering, where your current options are C and the JVM? How does Go fall down on that work load? I've got a fair bit of professional experience in both C (~10 years shipping code continuously in it) and Java, and I've spent the last couple weeks in Go --- not long enough to be a true believer, but enough to have some practical experience.