How I went about learning Rust

Re:How I went about learning Rust by lpapez on Friday July 15, 2022 @02:52AM (#32105395)

While Go is definitely fast enough for most scenarios, it is not the best language for low level code like drivers or kernel development.

Go was never ever intended for this purpose.

[ Parent | on HN ]

Re:How I went about learning Rust by cryptos on Friday July 15, 2022 @04:10AM (#32105901)

Yes, I know (although they promoted it as a "systems language", but it was not really defined what that should mean in the beginning), but it is a restriction, you don't have in Rust. Basically, Rust can do everything Go can do, but not the other way around. That _might_ help to make a decision for a language.

[ Parent | on HN ]

Re:How I went about learning Rust by stavros on Friday July 15, 2022 @05:38AM (#32106366)

Technically, assembly can do everything Rust can do, yet that doesn't help to make a decision for a language. Ergonomics matter.

[ Parent | on HN ]

Re:How I went about learning Rust by agumonkey on Friday July 15, 2022 @05:50AM (#32106432)

It seems to be an idiom shift. Systems means connected parts, go concurrency does just that, connecting parts through channels. But it's not `systems` as in bare metal electronic chips systems. More like IT `system`.

[ Parent | on HN ]