That bug was almost a year before Rust 1.0 was released. At this point, Rust is being used in production outside of Servo- for example Dropbox is even using it for their core data storage code.
It's certainly not as old-and-boring stable as C, but it's a lot closer than you'd think.
Re:Why I Write Games in C
by dunkelheit on Saturday January 09, 2016 @02:33PM
(#10872500)
And that bug was less than a 1.5 years before now. And Rust is at version 1.5 now. And all changelog entries since version 1.0 (which was released 8 months ago) mention "multiple bugfixes". Of course, that's all subjective, but for me these facts all scream "rapid pace of development, expect multiple annoyances and a couple of major bugs for your particular use case".
Dropbox is using Rust in production? Great news! But I'll wait when a thousand of organizations use Rust in production before advocating its use in my own organization. Also, judging by this comment: https://www.reddit.com/r/programming/comments/3w8dgn/announc... they had incredible rapport with the language core team. That is a luxury not every team using Rust is going to have.
Still, great news. I guess I must implement some kind of little personal project in Rust and in the process help iron out a few more quirks.
Re:Why I Write Games in C
by steveklabnik on Saturday January 09, 2016 @03:40PM
(#10872779)
As a member of that core team, I would expect that we will pay just as much attention to any company that plans on using Rust in production. We're very interested in supporting companies using Rust, and making sure t works well.
That doesn't inspire a ton of faith in Dropbox, TBH.
My comment is not meant to bash Rust, on the contrary it is very promising and the fact that it is used to write Servo is likely to significantly speed up its maturation. But as author notes, if you are developing a project under a deadline you don't have time for bugs you didn't cause yourself. So old boring technology is the way to go.