Slashdot Mirror
Rust Blog Touts 'What We Achieved' in 2017 (rust-lang.org)
An anonymous reader quotes the official Rust blog:
Rust's development in 2017 fit into a single overarching theme: increasing productivity, especially for newcomers to Rust. From tooling to libraries to documentation to the core language, we wanted to make it easier to get things done with Rust. That desire led to a roadmap for the year, setting out 8 high-level objectives that would guide the work of the team. How'd we do? Really, really well.
Aaron Turon, part of the core developer team for Rust, wrote the blog post, and specifically touts this year's progress on lowering the learning curve with books and curriculum, as well as actual improvements in the language and a faster edit-compile-debug cycle. He also notes new support for Rust in IntelliJ and Atom (as well as preview versions for Visual Studio and Visual Studio Code) in 2017 -- and most importantly, mentoring. I'd like to specifically call out the leaders and mentors who have helped orchestrate our 2017 work. Leadership of this kind -- where you are working to enable others -- is hard work and not recognized enough. So let's hand it to these folks...! Technical leaders are an essential ingredient for our success, and I hope in 2018 we can continue to grow our leadership pool, and get even more done -- together.
Aaron Turon, part of the core developer team for Rust, wrote the blog post, and specifically touts this year's progress on lowering the learning curve with books and curriculum, as well as actual improvements in the language and a faster edit-compile-debug cycle. He also notes new support for Rust in IntelliJ and Atom (as well as preview versions for Visual Studio and Visual Studio Code) in 2017 -- and most importantly, mentoring. I'd like to specifically call out the leaders and mentors who have helped orchestrate our 2017 work. Leadership of this kind -- where you are working to enable others -- is hard work and not recognized enough. So let's hand it to these folks...! Technical leaders are an essential ingredient for our success, and I hope in 2018 we can continue to grow our leadership pool, and get even more done -- together.
I'll just leave this here
It's like a mirror. If you go in being an ass, demonstrating an unwillingness to do anything but snark or bash or otherwise unproductively complain, then yes: you will be disappointed when the Rust community tells you to piss off, albeit in a slightly kinder manner.
I went in expecting a community of intolerant bigots after reading Slashdot's opinions, and found them to be a refreshing case of a community that's more interested in improving their product than it is in just fighting against the tides of trolldom. Some of their proponents have felt a little cultish at times, but that's par for the course for new languages in my experience, so I don't really understand why some people are upset about that.
Basically, whether or not the language is mediocre to you for some undefined reasons is kind of besides the point. It's what you can and want to do to make it better. They know there are problems, and they're working to address them. If you don't care to help, just snark (or go on an ill-informed rant) then you'll be rightly turned away.
Why do we compare Rust to C++? Shouldn't we compare it to Ada? I work on security in the auto industry. What is the point of Rust? I get how its better than C++ for security and safety, but how is it better than Ada? That's a far more fair comparison. Ada environments are more mature. The language has been used with great success in civilian avionics and DOD projects for decades. I've been trying to get people to think about Ada in automotive for years (and, with autonomous cars, there might be a very good justification finally for automotive software to be treated like civilian avionics software). No one in a mature industry like automotive is going to seriously consider Rust, but they might consider Ada. Why are we even talking about Rust? Is Ada not feminist enough!?...