← Back to context

Comment by SwiftyBug

12 hours ago

From your comment, I'm assuming you're mostly familiar with interpreted languages. Chances are that you know JS/TS. If that's the case, I suggest that you give Go a go. The learning curve is way softer than Rust's and it's not too uncomfortable to someone who already knows TypeScript. And the advantage of Go over Rust is that the compile time is much, much shorter.

I went from Bash to Go as a system admin, and eventually built something with Rust too, so I can definitely confirm that the Go learning curve is softer than Rust.

> From your comment, I'm assuming you're mostly familiar with interpreted languages.

I'm proficient with Python and Julia, but I avoid Python as much as possible.

> The learning curve is way softer than Rust's

Ok, it might be easier, but then I'll have learned Go and not Rust :-)

I still think it's better to learn Rust

https://www.youtube.com/watch?v=nOSxuaDgl3s

  • I only watch the go part, and I'll say that in 3 years working with I might have had at most 3 times nil pointer crashes in prod, in which took about 30 min between getting fixed and deployed.

    There are linter which helps prevent most of if not all crashes (just keep in mind to run linting and compile the binary it would still be ages faster than anything rust I have ever compiled). His argument is weak, and not simple.

    I'll give that type system in golang is too simplistic sometimes, and a more complex could help to express better some use cases.

    Still go for a person coming from a interpreted language is a solid choice by being MUCH MUCH simpler.

    • I agree on the easiness of Go, but I don't think people should always choose the easy solution. The easiness of Go come at a cost.

      1 reply →

    • I agree with simplicity and ease of learning Go.

      > 3 years working with I might have had at most 3 times nil pointer crashes in prod

      I've been running a rust app for my personal trading app and a small service at a very large FAANG company for more than 3 years, and guess what I'm yet to see a nil crash.