News for hackers. Stuff that matters.
Re:Announcing Tokio 0.1 by p0nce on Wednesday January 11, 2017 @04:54PM (#13377836)
I don't see an inaccurate statement on the Ruby frontpage: https://www.ruby-lang.org/fr/

edit: I'm just saying "don't lie". I shouldn't have to defend this view point and get downvotes for it.

Re:Announcing Tokio 0.1 by Manishearth on Wednesday January 11, 2017 @05:33PM (#13378106)
It's not a lie. Terminology has nuance, and its meaning may change based on context.
Re:Announcing Tokio 0.1 by p0nce on Wednesday January 11, 2017 @05:48PM (#13378183)
Look, it's really really simple.

1/ It says on the tin "prevents segfaults". It does not prevent segfaults in all cases, but OK, let's debate the other claim.

2/ It also says "guarantees thread safety". What is the Wikipedia definition of thread safety? It varies, so let's take the most common "freedom from race conditions."

Steve come and say Rust can have race conditions https://news.ycombinator.com/item?id=13376485 and that it's a common misunderstanding to think it prevents race conditions. Surely it would be great if the frontpage would not promote it!

Ergo the frontpage claim is false.

Re:Announcing Tokio 0.1 by Manishearth on Wednesday January 11, 2017 @05:57PM (#13378241)
I disagree with the segfaults bit (which is what you had been focusing on so far, and which is what I've been arguing against) but yeah, "guarantees thread safety" is iffy.

The wikipedia definition is pretty vague, it relies on a concept of "safe" that isn't defined there. It's acceptable to say that "data race safety" is "thread safety", though confusing. Rust's homepage does clarify what it means in the bullet points below that statement, so I wouldn't call this a lie. It may be misleading though, and this is a common misunderstanding as steve mentioned, so I submitted a PR to fix it https://github.com/rust-lang/rust-www/pull/685

Re:Announcing Tokio 0.1 by p0nce on Wednesday January 11, 2017 @06:06PM (#13378307)
Yes I think "data race freedom" when I see "thread-safety" (I despise this one term for being so vague).

In the punchline, "prevent segfaults" is framed in negative terms. If you put "provides memory safety" it will be a bit less evocative of specific pain, but will give a warm feeling.

Re:Announcing Tokio 0.1 by Manishearth on Wednesday January 11, 2017 @06:15PM (#13378370)
https://github.com/rust-lang/rust-www/pull/685#issuecomment-...

Not too sure of the segfaults bit, feel free to put in your thoughts on that PR

Re:Announcing Tokio 0.1 by steveklabnik on Wednesday January 11, 2017 @06:17PM (#13378392)
Yes, to second Manish, I would love to find something that is accurate, succinct, and understandable. Concrete suggestions (from you or anyone else) very welcome.
Re:Announcing Tokio 0.1 by p0nce on Wednesday January 11, 2017 @06:40PM (#13378531)
My attempts so far:

Rust is a systems programming language that runs blazingly fast, guarantees memory safety and provides correct concurrency.

Rust is a systems programming language that provides uncompromised performance, convenience and security.

Rust is a systems programming language that enables unprecedented levels of performance, productivity and safety.

edit: I like (2) best