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 :-)

Agree. I immediately remembered k9s[1], a TUI to manage Kubernetes workloads.

It is written in Go as well.

[1]: https://github.com/derailed/k9s

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

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.

Agree, people should understand why they are picking a language. If it is to learn new language that is fast, compiles to a binary (also fast) and has a nice onboard experience for a person coming from a interpreted language (which is the topic of thread) go fits nicely.

Rust is not always the answer just because it has "no nil exception". The correctness of Rust comes at a cost as well.

Why not C, C++, Go or any other compiled language? What made you want ot learn rust?

If it's good enough for Linus Torvalds, it's good enough for me :-)

I'm not a professional programmer, I just want to have more control over my computer. C seems like a full time job to learn and not shoot yourself in the foot.

There's also a program in Go which does almost the same: https://github.com/bluetuith-org/bluetuith

This is anecdotal but I've been using bluetuith for a year on my nix machine with several adapters then switched to bluetui recently, and my experience with bluetui has been amazing. I just ran into issues all the time with bluetuith and I assumed it was due to the OS or something. An example I can think of is trusted connections- my devices just never automatically connected once switched on, but now they do.

You can do it with any language that supports static linking, like C, C++, Go etc. You can also do it with things like Pyinstaller for Python. It's not that big of a deal tbh.

It absolutely is a big deal that you can run “cargo build” with no set up and things just work. Out of the languages you listed, Go is the other where it’s that easy.