4 ms·
Maybe somewhat rude question, but how close to being "ready" Rust is? I mean, should I start using it already if not only for the sake of language itself? How s
by krick 13y ago
Maybe somewhat rude question, but how close to being "ready" Rust is? I mean, should I start using it already if not only for the sake of language itself? How stable is it now? How much it will probably change 'till 1.0? How soon it can be expected to be "production ready"?
- panzi 13y ago1.0 is planned for this year. To the rest I don't know the answer. But you should use Rust so you might find problems and report them, because after 1.0 they can't do breaking changes.
- derekchiang 13y agoThe language will still change a lot before 1.0, so I don't recommend serious usage in production, unless you are prepared for updating your codebase every now and then. However, many people have already started using Rust for personal projects, and their feedback has been invaluable to the development of the language!
- steveklabnik 13y agoThere are three production deployments of Rust that we know about. The language won't change a whole lot, but the libraries will.
- renox 13y ago> how close to being "ready" Rust is? I think that this depends on your expectations, I was quite disappointed to find that there isn't a clean way to make 'unit types' (second, millisecond, meters, etc) in Rust.. I wouldn't use Rust for anything but toy project..
- wfraser 13y ago> there isn't a clean way to make 'unit types' (second, millisecond, meters, etc) in Rust.. Actually, there's this bit on Tuple Structs[1] in the tutorial: > Types like this can be useful to differentiate between data that have the same underlying type but must be used in different ways. struct Inches(int); struct Centimeters(int); [1] http://static.rust-lang.org/doc/master/tutorial.html#tuple-structs http://static.rust-lang.org/doc/master/tutorial.html#tuple-s...