Hacker News Reader

Comment by kibwen | Hacker News Reader

I don't think this is incompatible with Rust's goal, which is to bring safety to the sort of low-level domain where C is currently dominant and systems can't afford to be structured as isolated nodes communicating only via RPC. In contrast, Midori was aimed at a higher-level general-purpose domain, like Go (and Erlang, too, which is even better than Go at the "cluster of nodes" approach, yet doesn't have a type system at all).

View on HN

Could it be, that many desicions for Rust have been made to make it more appealing to C devs?

Like, opting out of purity annotations or forced immutability?

I'm not saying these desicions are good or bad, I don't know much about system programming. But I often ask myself what the main motivators for a language are.

FWIW,after spending a couple of years with rust as my primary programming language, I'm convinced that they made the right decision wrt mutability (immutable by default, but mutability availale when needed), as rust's lifetime system eliminates nearly all the remaining pain points around mutability (data races).

On the other hand, I think it is very important that some notion of purity be incorporated, even if only as an opt-in.

> spending a couple of years with rust as my primary programming language

Oh, how did you achieve that? :)

Probably not with too much difficulty. 1.0's alpha was nearly 2 years ago. The github repo goes back to mid 2010: https://github.com/rust-lang/rust/graphs/contributors

I didn't want to imply that Rust is to young for people to have been spending years using it.

I wanted to know how you could get a Rust-job (using it as primary programming language) today :)

Ah. So, most organizations using Rust in production are moving existing employees over or hiring more generally.

I'd hit up these people: https://www.rust-lang.org/en-US/friends.html

Forced immutability has enormous performance downsides in some cases. Rust can't have that.

Reply on news.ycombinator.com