Live data from Hacker News

Announcing Rust 1.0 Alpha

blog.rust-lang.org

51–60 of 255 posts

Re: Announcing Rust 1.0 Alpha

#51
post #47

Earlier quoted context omitted.

I think the stdlib is not the way to go. Give me an example of any ecosystem where the standard library is the defacto best solution? But would agree that the only thing Rust might need are officially supported crates, while keeping the language itself fully separate. The language is then completely free of the hastles of maintaining a stdlib that probably isn't used by most people anyway. But at the same time offici…

> Give me an example of any ecosystem where the standard library is the defacto best solution? In Go that's certainly the case and in my experience it's a great thing, only time will tell if it will end up suffering stagnation like maybe happened to python.

Or what happened to Java. And probably other ecosystems.

IMO a "softer", "recommended" packages approach is better longer term.

Re: Announcing Rust 1.0 Alpha

#52
post #41

Earlier quoted context omitted.

It's been my experience that the standard library is _never_ the place for the best lib to do $WHATEVER_PARTICULAR_TASK, but different folks have different preferences. We'll see how it all shakes out!

The useful thing about a standard library is that it provides a common vocabulary for code, which is a great help for interoperability. For example: c++ doesn't have a 3D vector class in its standard library, so pretty much every 3D-related library invents its own & you end up having to write lots of useless glue code to convert from one to the other.

I really love your usage of the phrase "common vocabulary" to describe the utility of the standard library. I'll be using it in every discussion of this sort from now on.

Re: Announcing Rust 1.0 Alpha

#53
post #11

> The core libraries are feature-complete for 1.0. Can someone well informed about Rust give some impressions on the standard library? It is as comprehensive as in python or Go for example?

Core team member here. The standard library is _not_ "batteries included," on purpose. Given that we have Cargo, and it works well, tying package updates to the language version has quite a bit of downside, and very little upside. That said, the Rust team itself maintains and provides a number of packages on Crates.io ourselves. Many of these were pulled _out_ of the standard library over the past few months.

> The standard library is _not_ "batteries included," on purpose. Given that we have Cargo, and it works well, tying package updates to the language version has quite a bit of downside, and very little upside.

With a good package management system, a batteries-included standard library could just be a set of packages where you are guaranteed that a version of each backward-compatible to the one provided at language release (in SemVer terms, a package with the same major version number as the one packaged with the language release) would be available and maintained for the maintenance life of the language version. It wouldn't have to prevent either bug-fixes to packages out-of-band with language version upgrades, or even out-of-band new major versions of packages that support the existing language versions so long as the old major version was maintained in parallel as long as the language version was.

Re: Announcing Rust 1.0 Alpha

#54
post #2

Great news! Have been waiting for 1.0 to jump into rust. Anyone knows when the final 1.0 will come?

TL;DR: twelve to eighteen weeks. Possibly more six-week increments after that, depending on how we feel during beta. Full details: http://blog.rust-lang.org/2014/12/12/1.0-Timeline.html

Congratulations! I look forward to seeing the ecosystem expand now that core has solidified. Very exciting.

Re: Announcing Rust 1.0 Alpha

#55
post #33
post #27

Earlier quoted context omitted.

Finally! I hadn't used Rust for two weeks, and when I downloaded the nightly last night, code from two weeks ago was breaking. Feature stability will help.

Yes, this is a big deal. I tried looking into Rust a couple of months ago, but the speed of change meant that blog posts and tutorials from just weeks before were sometimes completely broken. Getting to 1.0 means that the ecosystem has a chance to grow properly which means "lesser" coders such as myself have a chance to learn and get involved.

Tutorials should at a minimum be dated and if possible include the version of rust used when making the tutorial.

Re: Announcing Rust 1.0 Alpha

#57

I've been incredibly impressed by the willingness of the Rust team to take a step back and re-evaluate old decisions. I think this 1.0 release will be much better for all the iterations put into e.g. dynamically sized types and other things that never quite fit in their first half-dozen iterations of the design. Congrats all!

Thank you. Personally, I try to have strong opinions, weakly held. :)

Re: Announcing Rust 1.0 Alpha

#59
Wow. Anyone remembers Rust pre-0.1? When it had typestate, ML syntax, garbage collection, etc.? So nice to see how the language slowly evolved and was molded to fit as best as possible the problem they were trying to solve.
Post reply on HN