7 ms·
Async code is way nicer in Go than it is in Rust. It makes up for a lot for me when writing web services. Also Go is much easier to read vs Rust.
by qaq 4y ago
Async code is way nicer in Go than it is in Rust. It makes up for a lot for me when writing web services. Also Go is much easier to read vs Rust.
- Klonoar 4y ago>Also Go is much easier to read vs Rust. This is subjective - I for example have no real issues reading Rust code, but find Go to look like utter spaghetti on the screen.
- baby 4y agoThat’s probably because you’re not used to it. I think it’s common knowledge that Golang is easy to read.
- lsaferite 4y agoCouldn't the same be said of rust though? The biggest barrier, in my experience, is almost always familiarity with the syntax.
- Klonoar 4y agoPretty much this, yes. I think my comfort with Rust moreso comes from it feeling like any other C-ish language in appearance. It reads as expected to me.
- baby 4y agoI work mostly with Rust, and have been for years, and no I wouldn't say that Rust is easy to read. It's easier to read than most legacy languages, but it's nothing like Golang.
- qaq 4y agoSure. But just due to Go type system being pretty basic I've never came across Go code I could not immediately grock, not so with Rust. Even bugging some pretty savvy Rust devs for help it sometimes took them a decent amount of time to pin down whats going on.
- Tozen 4y agoI have to side with those saying Go has greater readability, and is easier to use and learn. I know there is a strong push (and arguably corporate backed) to put Rust in everybody faces or present it as being superior, but we still need to be realistic and honest. Not saying that Rust doesn't have its places where it can shine, just that a lot of people are going to find Go to be easier to deal with overall, and it was partially designed to be that way.
- Klonoar 4y ago>I know there is a strong push (and arguably corporate backed) to put Rust in everybody faces or present it as being superior No part of my comment was doing this, and this bit is entirely unnecessary and adds nothing to the comment you wrote except fan religious wars about languages.
- kaba0 4y agoAnd much more error prone.
- fnord123 4y agoDepends where someone comes from. If they are from a weakly or dynamically typed language (C, python, Javascript) then Go is quite ok. If you're coming from Haskell, OCaml, or Rust, then sure Go might be frightening.
- peaky_blinder 4y agoThey're all weakly typed languages but C is statically typed.
- kaba0 4y agoI think parent didn't say anything to the contrary, or maybe it was edited?
- fnord123 4y agoFirst iteration was didn't include the part about haskell/ocaml.
- simiones 4y agoPython is generally considered quite strongly typed, though dynamic. That is because Python has relatively few implicit conversions, and especially few that are surprising ("1" + 1 is an error, not 2 or "11"; and unsigned short + unsigned short does not equal a signed int).
- masklinn 4y ago> Async code is way nicer in Go than it is in Rust. That’s because Go does not have async code. It has sync code on an async runtime. Like e.g. Erlang/Elixir.
- throwaway2037 4y agoThis is an interesting comment. Is there a webpage where I can read more about this idea?
- sph 4y agoPerhaps https://journal.stuffwithstuff.com/2015/02/01/what-color-is-your-function/ https://journal.stuffwithstuff.com/2015/02/01/what-color-is-...
- throwaway2037 4y agoThat guy is a lengendary blogger! And I have read that post. It was very eye opening. I always struggle when I write an (internal) API that has sync (blocking) and async (non-blocking) sections and methods. It quickly becomes very difficult to reason about!
- qaq 4y agoExactly don't have to deal with red/blue functions