News for hackers. Stuff that matters.
Re:Announcing Rust 1.0 by kamaal on Friday May 15, 2015 @03:45PM (#9553173)
Can somebody explain for what kind of use cases would this be helpful to use?
Re:Announcing Rust 1.0 by steveklabnik on Friday May 15, 2015 @03:50PM (#9553197)
Any time 'it matters'.

There's lots of stuff that we build, and we say things like, "Language X is slow, but it doesn't matter." "Language Y uses a lot of memory, but it doesn't matter." This is very, very often true. But every once in a while, it really matters.

That's when you want something like Rust. When the details are important. When you need full control, but you'd like a compiler to help catch your mistakes. When a garbage collector has too much overhead. When you need to write something inside of Language X or Y, instead of a C extension, you can use Rust.

Basically, anywhere you'd use C or C++, Rust is a great fit. Elsewhere? Maybe, maybe not. Depends.

Re:Announcing Rust 1.0 by robertfw on Friday May 15, 2015 @06:18PM (#9554037)
> When you need to write something inside of Language X or Y, instead of a C extension, you can use Rust.

Are there any examples/discussion/information for interacting with rust from python, like you would a C extension?

Re:Announcing Rust 1.0 by steveklabnik on Friday May 15, 2015 @06:35PM (#9554098)
I devoted a whole chapter of the book to Ruby/Python/node embedding: http://doc.rust-lang.org/book/rust-inside-other-languages.ht...

A Ruby gem in Rust was one of our earliest production uses.

Re:Announcing Rust 1.0 by barosl on Friday May 15, 2015 @06:39PM (#9554119)
There's a wonderful presentation on this topic: https://www.youtube.com/watch?v=3CwJ0MH-4MA
Re:Announcing Rust 1.0 by madez on Friday May 15, 2015 @03:53PM (#9553220)

    Rust is a systems programming language that runs blazingly fast,
    prevents nearly all segfaults, and guarantees thread safety.[1]
So, if you care for low memory usage, execution speed or safety guarantees especially for hard-to-debug kind of errors, then Rust might be interesting for you.

It offers low-level access like C or C++ but excels with vastly improved security. So, I'd take that step, and say that where C or C++ is used right now, you might want to use Rust in the future.

[1] http://www.rust-lang.org/

Re:Announcing Rust 1.0 by blake_himself on Friday May 15, 2015 @04:46PM (#9553586)
Re:Announcing Rust 1.0 by madez on Friday May 15, 2015 @05:15PM (#9553720)
Give it some time to mature. Today is the day of the language specification, not the finalization of the toolchain.

The Rust language offers low-level access with amazing security guarantees, and is working on an optimizing toolchain.

Let me take Python as a comparison. It has fundamental[1] roadblocks for being fast on current and probably future hardware, because its dynamic nature requires many indirections which are problematic for CPU cache efficiency.

Will Rust always be faster than C? Probably not, but that is not needed to be blazingly fast. What is important is that there are no fundamental difficulties to be as fast as C.

[1] I know, you can work around some of those indirections.

Re:Announcing Rust 1.0 by blake_himself on Friday May 15, 2015 @05:54PM (#9553912)
> Will Rust always be faster than C?

(By 'always' did you mean 'ever'?)

That may be so, but their advertising gives the wrong impression. They should keep their claims muted until they can back them up.

Re:Announcing Rust 1.0 by madez on Friday May 15, 2015 @06:09PM (#9553985)
If you consider that robust and memory efficient parallelization is way more easily achieved in Rust than in C, Rust might already win today for some applications if you limit the developer time. In C it's hard to fulfill the requirements at all.
Re:Announcing Rust 1.0 by steveklabnik on Friday May 15, 2015 @05:00PM (#9553668)
We haven't paid any attention to those benchmarks in a long time. When we did, we even beat C and C++ sometimes.
Re:Announcing Rust 1.0 by igouy on Friday May 15, 2015 @09:41PM (#9554676)
Are you paying attention to some other benchmarks that you could share when responding to these questions?

Just trying to dismiss measurements that are publically available, without putting forward something you consider better, is kind-of…

Re:Announcing Rust 1.0 by steveklabnik on Monday May 18, 2015 @12:45PM (#9565405)
No, as optimizing performance hasn't been a focus, shipping good language semantics has been.
Re:Announcing Rust 1.0 by igouy on Tuesday May 19, 2015 @12:56PM (#9571482)
Humbly suggest the "optimizing performance hasn't been a focus, shipping good language semantics has been" message needs to be repeated louder and clearer.

The expectation that has been created is - "Rust is a systems programming language that runs blazingly fast" - and that may lead to disappointment.

Re:Announcing Rust 1.0 by steveklabnik on Tuesday May 19, 2015 @02:35PM (#9572183)
Just because there may have been a regression on a particular benchmark doesn't mean that Rust is not generally fast.
Re:Announcing Rust 1.0 by igouy on Tuesday May 19, 2015 @09:32PM (#9574197)
imo it would be helpful to you all, to set a clear expectation that performance will be a priority in some future version but has not been so far. (As that's what you seem to have just said.)

That's all. No reference to "a particular benchmark", or whatever you take "generally fast" to mean.

Re:Announcing Rust 1.0 by blake_himself on Saturday May 16, 2015 @03:59AM (#9555358)
http://www.areweblazingfastyet.org is free - you'd better grab it before I do :). If you don't take it, I'll just make it return those pieces of the language shootout.