This is usually a very simple decision. Do you need the performance of Rust? If not, use Go (or Java or F# or C# or whatever GC language you prefer)
Finally, a pragmatist on this Rust vs Go maddness. Thank you
Should I Rust or Should I Go?
121–130 of 178 posts
Re: Should I Rust or Should I Go?
#122As someone building my startup [0] on Rust (and a fan of the language since ~2014) I don't think this is a very compelling list of points. > Rust is overhyped People are excited about Rust! Not sure why this is a reason you _shouldn't_ use the language. > Rust projects decay The text doesn't match the headline here; Rust takes backwards compatibility very seriously, and rust code I wrote in 2016 against Rust 1.10 sti…
> ZGC, GraalVM, and Project Loom which essentially makes Java a better Go.
GraalVM is still nowhere near as nice as Go when you need to compile quickly. Last time I checked, the compiler needed orders of magnitude more time and memory to make a binary. ZGC is pretty nice, though.
Re: Should I Rust or Should I Go?
#123In what world is Go more reliable or faster than Java? Especially modern Java (or other good JVM languages like Kotlin). It compiles faster but that is about it. Which is a good thing too because it's verbose AF and heavily reliant on code generation even after generics shipped so that compiler lines/s actually matters. The only knock you can put on Java for reliability is null-safety but lets be real, nil pointers,…
The usual Java bashing from Go folks, meanwhile Google keeps mostly using Java, Kotlin and C++, with only a couple of key projects using Go, like Kubernetes or Google downloader.
I work in cloud and every single one of our new projects is in go
Re: Should I Rust or Should I Go?
#124Earlier quoted context omitted.
> Java is easily faster and more reliable than Go I work in Java for my day job and I disagree. 1. Cold starts for Java serverless (lambda) are worse than scripting languages 2. For everything else, Java uses 5-10x more memory than Go. The memory overhead difference is really noticeable while the CPU difference is often similar.
> Cold starts for Java serverless (lambda) are worse than scripting languages I've run plenty of Java applications in Lambda and they are pretty fast (like done in a few minutes fast). I've yet to try SnapStart which can make those workloads even faster.
I have successfully written entirely serverless APIs in Go. It’s not a great fit for everyone, but was for our use-case. Cold-starts became a non-issue compared to Java.
Re: Should I Rust or Should I Go?
#125As someone building my startup [0] on Rust (and a fan of the language since ~2014) I don't think this is a very compelling list of points. > Rust is overhyped People are excited about Rust! Not sure why this is a reason you _shouldn't_ use the language. > Rust projects decay The text doesn't match the headline here; Rust takes backwards compatibility very seriously, and rust code I wrote in 2016 against Rust 1.10 sti…
Nim is another alternative. Fast to write and excellent performance. Needs a bigger community though.
Re: Should I Rust or Should I Go?
#126As someone building my startup [0] on Rust (and a fan of the language since ~2014) I don't think this is a very compelling list of points. > Rust is overhyped People are excited about Rust! Not sure why this is a reason you _shouldn't_ use the language. > Rust projects decay The text doesn't match the headline here; Rust takes backwards compatibility very seriously, and rust code I wrote in 2016 against Rust 1.10 sti…
Why not Kotlin instead of Java? I feel Kotlin is very underrated.
Re: Should I Rust or Should I Go?
#127In what world is Go more reliable or faster than Java? Especially modern Java (or other good JVM languages like Kotlin). It compiles faster but that is about it. Which is a good thing too because it's verbose AF and heavily reliant on code generation even after generics shipped so that compiler lines/s actually matters. The only knock you can put on Java for reliability is null-safety but lets be real, nil pointers,…
Go's GC is much more naive than modern Java GCs, and the codegen is not terrific. That said: A few design decisions in the Java language (that are only slowly getting fixed) harm performance: 1. "Everything is virtually dispatched" reduces the ability to make inlining decisions sensibly. 2. Escape analysis gets harder (and less effective), leading to moving fewer variables onto the stack. 3. The poor support for allo…
> "Everything is virtually dispatched" reduces the ability to make inlining decisions sensibly.
you can use "static" keyword?..
> Escape analysis gets harder (and less effective), leading to moving fewer variables onto the stack.
does go have the same idea of escape analysis with benefits and issues?..
Re: Should I Rust or Should I Go?
#128Earlier quoted context omitted.
Go's GC is much more naive than modern Java GCs, and the codegen is not terrific. That said: A few design decisions in the Java language (that are only slowly getting fixed) harm performance: 1. "Everything is virtually dispatched" reduces the ability to make inlining decisions sensibly. 2. Escape analysis gets harder (and less effective), leading to moving fewer variables onto the stack. 3. The poor support for allo…
> "Everything is virtually dispatched" reduces the ability to make inlining decisions sensibly. you can use "static" keyword?.. > Escape analysis gets harder (and less effective), leading to moving fewer variables onto the stack. does go have the same idea of escape analysis with benefits and issues?..
Static == final?
Re: Should I Rust or Should I Go?
#129Earlier quoted context omitted.
> "Everything is virtually dispatched" reduces the ability to make inlining decisions sensibly. you can use "static" keyword?.. > Escape analysis gets harder (and less effective), leading to moving fewer variables onto the stack. does go have the same idea of escape analysis with benefits and issues?..
Static == final?
static methods, they won't be virtually dispatchable, and will be potentially inlined.
Re: Should I Rust or Should I Go?
#130Ok, so I'm no expert on Rust or Go or whatever, but I've noticed that many posts and comments seem to rip on Go, and that Go is bad, Rust is better, language X is better than Go, etc etc. My question is why all the hate on Go? And if Go is so bad as these posts claim, why compare everything against it? I'm not saying Rust isn't good or anything like that, but why the never ending hit pieces on Go? Lets just evaluate…
[deleted]