I think it’s cool as fuck.
On average same speed as c++, thread safe, memory safe, helpful compiler, friendly community.
LITERALLY FUTURE.
Opinions on Rust
Josiah Peterson
Other urls found in this thread:
rust-lang-nursery.github.io
twitter.com
Kevin Nelson
It's a good try. It really needs to get a faster compiler, though. And a second, GCC-based compiler.
Logan Cooper
Compilation speeds for Rust isn't fast as C compilers, but is definitely faster than C++ compilers.
James Moore
how is the gui support? i.e. qt, gtk, etc. bindings? does it "just werk" or do you have to go through a bunch of hoops to get it to compile on linux/windows/mac?
Ian Rivera
I support this language being the next main programming language of choice for system programmers and general application development. With my support being known, I know Rust's future as King in the near future is dubious at best. C++ was suppose to be the successor to C and it is, but there are plenty of people out there in the world living with us mind you, that still use C!
Isaiah Lewis
My opinion is that it's a bit of a weak NIH variant on C++.
It'd have been amazing to have this language at the time when LLVM didn't exist, GCC was half-assed, Windows was dominant, C++ stagnated and Microsoft's shit stack took over for superior Borland tooling when Borland fucked up.
Now that C++ is moving at a good pace again, I don't really see the point. But to each their own.
Isaiah White
I stopped writing it because the compiler and Cargo is too slow. I don't give a shit how good the language is if it takes 15 minutes+ to compile an average size project.
Zachary Richardson
Compilation speeds have improved for me since the last few months. If I recall correctly, it was around the same time I got a newer desktop setup.
Joshua Davis
You would have a point if people actually used those new features and the old parts were being deprecated. At best you have some disgusting inconsistent mix of C++11 and C++98.
Daniel Stewart
This would dramatically improve the quality of the language by folds. Unfortunately, the standard committee does not see this and opts to keep the crusted shit to keep C++ backwards compatible with code that uses a previous standard.