Rust the C replacement

http://esr.ibiblio.org/?p=7294&cpage=1
In practice, I found Rust painful to the point of unusability. The learning curve was far worse than I expected; it took me those four days of struggling with inadequate documentation to write 67 lines of wrapper code for the server.

Even things that should be dirt-simple, like string concatenation, are unreasonably difficult. The language demands a huge amount of fussy, obscure ritual before you can get anything done.

The contrast with Go is extreme. By four days in of exploring Go I had mastered most of the language, had a working program and tests, and was adding features to taste.

>>48
Nope. Caching is the #1 performance enhancing algorithm.
Your CPU has 3 levels of caches. OS has disk read/write caches, your IO library has cache buffers, your browser stores render pages in cache, Cache servers store static copies of websites to get the downloads faster. Caching is everywhere, even your desk is a cache of all important items in the room.