News for hackers. Stuff that matters.
Re:Go: Planning the 1.5 release by melling on Tuesday December 02, 2014 @11:23AM (#8687854)
If the release candidates are a few weeks out then it must be beta and very close to stable? Can anyone who's using Rust daily discuss performance and reliability. It should be ready for weekend projects.
Re:Go: Planning the 1.5 release by jakevn on Tuesday December 02, 2014 @12:00PM (#8688109)
They have 31 blocking issues to take care of before 1.0 is a possibility: https://github.com/rust-lang/rust/milestones/1.0

The project has 2,100 open issues and 8,500 closed issues.

The stability more or less comes down to the community moving away from targeting nightly, and that can only happen when all of the fires are put out. There are still a lot of breaking changes and clean-up being done in the final hour.

Some people consider stable to mean that the language is "production ready", which often implies a complete set of common libraries. There is still a lot of work to be done in this regard after 1.0. Doing the nightly build whack-a-mole is too frustrating for many, though, so 1.0 will help a lot for developing the ecosystem that a "public ready" language needs.

Re:Go: Planning the 1.5 release by gtani on Tuesday December 02, 2014 @06:14PM (#8690745)
I recommend looking at "This week in" blog and the RFC's also, to form your own opinion of stability

http://this-week-in-rust.org/

https://github.com/rust-lang/rfcs#active-rfc-list

__________________________

discussion re: stdlib and 1.0 https://www.reddit.com/r/rust/comments/2mo0zb/the_race_towar...

Re:Go: Planning the 1.5 release by jakevn on Thursday December 04, 2014 @03:02PM (#8701298)
Thank you for this. I thought this-week-in-rust stopped a while ago. Very useful!
Re:Go: Planning the 1.5 release by kibwen on Tuesday December 02, 2014 @11:59AM (#8688101)
Weekend projects certainly, but I'd still off from doing anything super serious because there are still a few breaking changes waiting in the wings (such as the finishing touches on closure reform), as well as a few potential last-minute syntax tweaks that are still being considered (though if accepted those should be trivial enough to migrate via an automated tool).