To give an example, I don't believe that this code:
https://github.com/chris-morgan/rust-http/blob/master/src/ex...
is any less cohesive than this:
https://gist.github.com/thisishugo/8433714
Obviously each to their own, but I'm finding Rust a very enjoyable language to work with.
Rust at least tries to make an honest effort to change that. If and when it gets really fleshed out it'd be a boon to all those poor developers. And please forget your awfully subjective qualms about syntax (seriously, go and program in Haskell if you're all for pretty syntactic and cohesiveness - though I can't guarantee you won't find it "disgusting"). Memory management in the C++ way is bloody hard, and it's a dirty affair. It makes no sense to be repulsed by all the complexity there, because it's unavoidable, and it's a job that has to be done. Of course there's going to be a smattering of syntactical constructs to make memory management less tedious, just like there is extra syntactic baggage on bigger Haskell programs to accommodate the fine control over side effects.
Having a memory safe high-performance language with C++-like memory management is a HUGE thing. A while ago I would have dismissed such a thing as a pipe dream, and when I became convinced that Rust could work it was a moment of great rejoicing. Even if Rust ends up on the dumps, there has been at least an effort, and maybe someone will make a better Rust some day.
So please try to understand the purpose and rationale behind Rust before dismissing it in a superficial way.
There have been alternatives in the form of Ada, Modula-3 and Oberon, Cyclon and a few others.
Except for Ada, they were left in the research labs.
Looking to the history of systems programming languages, the only ones that have become mainstream have an OS vendor to thank for.
So which OS vendor will push for a C++ alternative?
[1] https://github.com/Yoric/Mozilla-Student-Projects/issues/33
For running inside the browser I rather stay with JavaScript and friends.
D isn't safe if you don't use the GC.
Go is a fully garbage collected language that doesn't offer a lot of support for manual memory management (and that isn't intended to attack Go—it just wasn't one of its goals). Rust is a low-level systems language that allows full control via zero-cost abstractions, but is safe. Achieving that goal requires some new machinery and syntax. Systems programming often entails writing for environments in which you can't use a GC (or even any runtime at all) for performance or other reasons.
> Also your point about syntax vs safety and correctness makes no sense, since it implies that those are mutually exclusive so I'm just going to ignore that one.
Rust has a unique feature—manual memory management with safety—so it needs syntax for it. It's not just syntax for its own sake—it's what gives the language a niche all its own.