Hacker News Reader

Closures are soooo messed up right now, because we're in the process of replacing them wholesale but the new system is only half-implemented. As a result you're forced to choose between using closures that work but suck (the old system) or closures that don't suck but don't work (the new system). So don't judge us on closures just yet. :)

View on HN

I hope that when Rust hits 1.0 -- they take backward compatibility exceptionally seriously. The pre-1.0 path has been exceptional wild ride, and it has made me a bit gun shy about the language as a whole.

I am no stranger to pre-1.0 languages, I have worked with lots of them, but none have been as frustrating (or interesting) as Rust... the question as to will Rust grow into a production language or an academic toy still remains an open one in my book.

Reserving judgement until 1.0 is out.

> I hope that when Rust hits 1.0 -- they take backward compatibility exceptionally seriously.

We do and we will. It's one of the reason there's such churn right now: we can't keep doing that post 1.0.

Look what just appeared http://blog.rust-lang.org/2014/10/30/Stability.html

I can't decide if that terrifies me or inspires confidence. But, it is great to see it on the radar and out in public.

Reply on news.ycombinator.com