Reasons not to use Rust

- You think programming languages should be closed and proprietary
- You like random pauses caused by forced collection of the garbage
- You think program start-up should take minutes so you use stupid VM-languages instead
- You like broken features and memory corruption
- You sell hardware and want to deploy inefficient scripting languages only to sell more
- You only do pure programs that don't interact with the world
- You are a retard who doesn't understand the concept of ownership

Anything else?

>>80

And here I thought Python's ``developers are too stupid to format their code or press ctrl-shift-f in their IDE to clean up messy code'' mentality was the worst.

This isn't a problem. There are ~infinity ways to represent what you want to loop over in Rust and you can plug most of them into for.

If you want to complain about not trusting the users, just look for evidence of their policy against implementing anything that was a good idea in Haskell. The core devs seem to hate the fact that, yes, actually, you do need to have monads in Rust (Result, Option.)

But even with their thought-policing, the Rust project comes nowhere near Python's self-sabotage for the sake of meaningless dogma.

>>92
U MENA range_step

Oh they renamed it because people are fucking idiots: http://doc.rust-lang.org/std/?search=range_step