https://github.com/rust-lang/llvm/blob/rust-llvm-2014-06-28/...
Very much so, agreed. It is a PR game most of all. It is unfortunate. But it is probably a game that needs to be played. I know microbenchmarks are bogus, but I still click and look at them.
Not really. The language is supposed to catter to professional programmers, not script kiddies.
The script kiddie's takeaway is: "well, C is still twice as fast as Rust!" The real professional's takeaway is: "wow, Rust manages to get within 4% of C while using iterators and higher order functions in the inner loop! Also: "Rust can do inline assembly too if that's what I need." https://gist.github.com/luqmana/5150557
* runtime systems * detailed memory management * algorithmic complexity
Yet, quite a lot of those build parts of huge systems that work and meet business requirements all the time, which makes them very desirable professionals.
Being able to competently benchmark is a fringe skill.
In any case, I don't think Rust's target group doesn't know about runtime systems, detailed memory management and algorithmic complexity.
After all it's mostly if you care about all three that you'll consider Rust.
E.g From dictionary.reference.com:
noun: - a person who is expert at his or her work: You can tell by her comments that this editor is a real professional. - a person who engages in an activity with great competence
adj: - extremely competent in a job, etc - (of a piece of work or anything performed) produced with competence or skill
For example, someone writing a huge distributed video processing system rarely needs to consider any of these topics. Because everything needed in that range is built. Making sure that the data is at the right place at the right time and predicting that needs none of the skill given by you. Is that person not a professional?
Sorry?
Expecting professional programmers to be familiar with "runtime systems, detailed memory management and algorithmic complexity" is "elitist as hell"?
That's one of the reasons the industry is lead by charlatans pushing the latest fad, doesn't know it's own history, and has built pile upon pile of cruft.
>For example, someone writing a huge distributed video processing system rarely needs to consider any of these topics. Because everything needed in that range is built.
Blind reliance upon things build by others, the characteristics of which one building the "video processing system" you describe is not able to assess, and is not able to modify to suit the project's specific needs. That we accept that is a lowering of the profession. It's like doctors deciding it's no need to know pathology and anatomy anymore, because there are expert systems they can use.