Or it could be that this post is just the beginning of his journey of learning & blogging about Rust. He did post another one 4 days later, albeit not yet touching on the topics you mention:
http://relistan.com/a-pattern-for-wrapping-c-function-calls-...
I've been looking into Rust during the past few days and I must say I got stuck on the memory model - all the different pointers and their interaction with ownership and mutability, closures capturing their environment (variables outside the closure in the scope where the closure is defined), reference binding, and then things like std::Cell which on the one hand seems to be an alternative to std::Option but on the other hand it's using some unsafe operations in its implementation to change mutability or something... It's quite confusing and it stopped me from writing a simple example application I wanted to write because I wanted to understand what's going on a bit better first.
@ is going to sink into the library and will be deemphasized in the language to help with this. That leaves only ~ (pointers) and & (references).
> closures capturing their environment (variables outside the closure in the scope where the closure is defined)
Right, this is one of the difficult pieces. This is going away as well in favor of Java-like Runnables to make the variable capture easier to understand (with macro sugar to make them just as convenient as closures). The closures that remain will work just like the closures you know from other languages regarding variable capture, and the Rust-specific stuff regarding variable capture will be gone.
> std::Cell
Yeah, this needs to be better documented. Part of the problem is that we haven't totally nailed down what Cell will be used for yet.
1. avoid dynamic allocations (limit yourself to stack-only objects) and you'll get rid of those fears for memory management
2. limit yourself to functional programming and you'll get a pretty good concurrent-ready code
For this "I need a new language" stance you'll need some better reasons.
The second sentence:
> I want a language where I can be much more productive than in C: one in which I do not fear the correctness of my memory management, and don’t have to go through major gyrations to write concurrent code.
And we see no explicit demonstrations of the memory management and no demonstrations at all of the concurrency model. It feels like the author had a more fleshed out post in mind, but either decided it was running too long or got bored before reaching the conclusion. :\