Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Should I Rust or Should I Go?

kerkour.com

Post reply on HN
Print view View original

81–90 of 178 posts

Re: Should I Rust or Should I Go?

#81

Post by eikenberry »

seurimas wrote: post #26

The features vs versions graph is more than a little nonsensical, and its conclusions even more so. > They should be stable and move slowly so that most of the time of your develoeprs is not spent fighting with their tools. I can't speak to Go's tooling base, but Rust's is head and shoulders above any other ecosystem that I've had to work with. This is definitely more a point in Rust's favor than against.

Go's tooling is much better in one key aspect, compile times. Rust's compile times and feedback loop are terrible and it is not a community priority (ie. they want to make it faster, but only incrementally and not the orders of magnitude improvement it needs). Go's could be better but at least it is a priority.

Re: Should I Rust or Should I Go?

#82

Post by eikenberry »

Which do you like better? Programming languages are not things to be judged based on some random criteria, but by how well they fit how your mind works and let you express the ideas you want to express. Different languages hit these points for different people.

Best advice you'll get is to try both (and more) and use the language you like best and that best aligns with the type of work you enjoy.

Re: Should I Rust or Should I Go?

#83

Post by vrmiguel »

eikenberry wrote: post #82

Which do you like better? Programming languages are not things to be judged based on some random criteria, but by how well they fit how your mind works and let you express the ideas you want to express. Different languages hit these points for different people. Best advice you'll get is to try both (and more) and use the language you like best and that best aligns with the type of work you enjoy.

One point that a lot of those "actually, just use Go" articles fail to recognize is that there is a sizable amount of developers who simply dislike programming in Go.

Despite its impressive compilation speed and bundled tooling and whatnot, some (myself included) find it tedious and uninteresting to program in Go, with tons of repetition and verboseness. Some people are more utilitarian and don't mind, but not all think the same.

Re: Should I Rust or Should I Go?

#84

Post by geodel »

pjmlp wrote: post #45
Xeoncross wrote: post #22

Earlier 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.

1. Ever thought about using class caches, AOT compilation e.g. OpenJ9, GraalVM,...? 2. Most of the time, a signal that the wrong algorithms and data structures are being used Amazon isn't rushing to rewrite their infrastrure from Java into Go.

Why would they rush? Customer will ultimately pay for infrastructure not Amazon.

Re: Should I Rust or Should I Go?

#85

Post by jackmott42 »

techn00 wrote: post #19

I'm a little tired of this endless discussion ... it always pops up with programming languages, they are tools, use whatever is more fit for what you're doing, move fast, break things, learn

This is about how to determine what is more fit for what you are doing.

Re: Should I Rust or Should I Go?

#86

Post by sharts »

jpgvm wrote: post #17

In 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,…

Embedded devices?

Re: Should I Rust or Should I Go?

#87

Post by eikenberry »

vrmiguel wrote: post #83
eikenberry wrote: post #82

Which do you like better? Programming languages are not things to be judged based on some random criteria, but by how well they fit how your mind works and let you express the ideas you want to express. Different languages hit these points for different people. Best advice you'll get is to try both (and more) and use the language you like best and that best aligns with the type of work you enjoy.

One point that a lot of those "actually, just use Go" articles fail to recognize is that there is a sizable amount of developers who simply dislike programming in Go. Despite its impressive compilation speed and bundled tooling and whatnot, some (myself included) find it tedious and uninteresting to program in Go, with tons of repetition and verboseness. Some people are more utilitarian and don't mind, but not all th…

Yep. For me Concurrency and CSP are why I learned Go and why I still use it today. I love thinking concurrently about problems and how data and control flow through those systems. It was a natural fit for me in those aspects and the other language warts don't get in the way enough to matter.

Re: Should I Rust or Should I Go?

#88

Post by taylodl »

Should I Rust or should I Go now?

Should I Rust or should I Go now?

If I Go there will be trouble!

If I Rust it will be double!

So you gotta let me know!

Should I Rust or should I Go?!

(I'll see myself out now...)

Re: Should I Rust or Should I Go?

#89

Post by zeroc8 »

axegon_ wrote: post #70

Honestly? Though I am forced to write go at work, I take Rust in a heartbeat(and it is a constant moaning from my end to ditch go and use Rust all the way almost every day). First thing to keep in mind is that Rust today is nothing like the Rust of 2015, even 2020. Way too many things are wrong with go: The packaging is one thing which I absolutely hate. I can't find words to express how much I hate the import "githu…

C looks like a toy language too, when compared to C++. And yet some of the best software in the world is written in it.

So yes, Go has its drawbacks. But it is easy to get things done with it.

Re: Should I Rust or Should I Go?

#90

Post by icholy »

dontlaugh wrote: post #40
seurimas wrote: post #26

The features vs versions graph is more than a little nonsensical, and its conclusions even more so. > They should be stable and move slowly so that most of the time of your develoeprs is not spent fighting with their tools. I can't speak to Go's tooling base, but Rust's is head and shoulders above any other ecosystem that I've had to work with. This is definitely more a point in Rust's favor than against.

Go’s is ok. Not as good though.

Can you provide an example of where rust has better tooling than Go?
Post reply on HN