News for hackers. Stuff that matters.
Re:My experience rewriting Enjarify in Rust by steveklabnik on Monday September 19, 2016 @01:51PM (#12533255)
Patrick already got into the subjectivity aspect here, so I'll leave that subthread there.

  > Rust eschews readability by erring on the side of terseness
We actually used to be more terse, then slowly expanded things until it felt right. At one point in time, "return" was "ret".

  > I can't understand who thought using ' was a great idea.
We had a lot of discussion about this before 1.0, and nobody was able to come up with a proposal that was clearly better.

  > I wish more time was spent on the visual aspect of a language.
We did spend a lot of time on this, and are continuing to. For example, the rustfmt team is just getting going, to nail down the last bit of style guidelines. Rust has had many different syntaxes over the years, and this is what we arrived at. See that other thread on subjectivity; I actually really like the "C with a bit of ML sprinkled in" that we arrived at. The only thing I don't like at all is the turbofish, ::<>, but I understand why it exists, it's almost never required, and it at least has a fun name to take some of the edge off. That said, I've also gotten less and less opinionated about syntax over time; semantics is far more interesting. As long as everything is consistent, I don't care as much about the specific details.
Re:My experience rewriting Enjarify in Rust by S_I on Tuesday September 20, 2016 @02:14AM (#12537484)
"C with a bit of ML sprinkled in" is IMO quite an understatement. ML is all over the place.

Personally i would have been happier if Rust had become "C with only the borrow checker and nothing else".But the community decided differently, and that's OK too.

I'm a low level guy (embedded and systems stuff) and what i would hate in our codebase is if look at line of code and find x numbers of concepts in it.

Nevertheless i applaud what you and the Rust community achieved, but my impression is that you'll be going the C++ way. Why? I follow the discussions of the Rust community about the future of the language, and there's always this "if we only add this one more feature" (for example see discussion about GC).

P.S.: For everyone saying "just use the features you need", no, this won't work. If they are available, people will (a)use them (see C++).

Edit: Typo.

Re:My experience rewriting Enjarify in Rust by rabidferret on Tuesday September 20, 2016 @01:47PM (#12541484)
> it's almost never required

Mate you should try Diesel or Futures. ;)