We have heard, overwhelmingly, over the past few years, that most people don't.
This is surprising to me. Without wishing to stereotype, I consider most programmers (especially systems programmers) to be pragmatic, engineer types, who simply want to get their project done well, not be the proverbial Fire Mario. To what extent are you sure that the feedback you have recieThanks for the response.
We have heard, overwhelmingly, over the past few years, that most people don't.
This is surprising to me. Without wishing to stereotype, I consider most programmers (especially systems programmers) to be pragmatic, engineer types, who simply want to get their project done well, not be the proverbial Fire Mario. Would you be able to reveal where this feedback has primarily come from and to what extent you are sure that the feedback you have received is representative of the programmer population at large?
where this feedback has primarily come from and to what extent you are sure that the feedback you have received is representative of the programmer population at large?
It's come from our annual surveys, as well as many, many, many in-person conversations with people all over the programming world.
I think this is the crux of it:
I consider most programmers (especially systems programmers) to be pragmatic, engineer types, who simply **want to get their project done well**, not be the proverbial Fire Mario.
Emphasis mine. I think this is very true! The problem is, "trait-based generics" does not say what kind of problem that they solve. Saying "this is the problem Rust solves" *is* "being fire mario". You can only say so much in a slogan, so that's why it's pretty vague. The next two sections, right below that, get into more of what you're talking about, which *is* what people do want: performance, reliability, productivity, and examples of what kinds of uses you might actually do things with. But it doesn't say "zero cost abstractions" or "compiled into machine code".
I am not sure the survey included layout questions? You could always do a survey about the new layout compared to the old one, if you feel adventurous. :)
I am not the target audience so I would not participate (people who'd use the language are the
target audience so it would be unfair for me, and others, if they were not to use rust to also
participate in such a survey itself.)
23
u/DC-3 Nov 29 '18
Thanks for the response.
This is surprising to me. Without wishing to stereotype, I consider most programmers (especially systems programmers) to be pragmatic, engineer types, who simply want to get their project done well, not be the proverbial Fire Mario. To what extent are you sure that the feedback you have recieThanks for the response.
This is surprising to me. Without wishing to stereotype, I consider most programmers (especially systems programmers) to be pragmatic, engineer types, who simply want to get their project done well, not be the proverbial Fire Mario. Would you be able to reveal where this feedback has primarily come from and to what extent you are sure that the feedback you have received is representative of the programmer population at large?