Live data from Hacker News

Dave Herman’s contributions to Rust

brson.github.io

11–20 of 174 posts

Re: Dave Herman’s contributions to Rust

#11
post #4

Haven’t learned Rust yet. I see they debated this: let and let mut let and var And went with the verbose option. Swift went with the succinct option, which I love about the language. In practice I suppose I do mostly type “let” in Swift so it doesn’t matter much Swift, however, chose ‘func’ instead of ‘fn’, after much debate. Those little things that are debated initially, then forever

Kotlin's version is even better: val & var Super clear. The "let" version smells a lot of "I have a CompSci PhD".

No, not at all. I hate var & val because I never can remember which is which (from Scala, which I never really used a lot).

let vs let mut is /clear/ - you can simply not mix them up.

Re: Dave Herman’s contributions to Rust

#12
post #9

Earlier quoted context omitted.

Kotlin's version is even better: val & var Super clear. The "let" version smells a lot of "I have a CompSci PhD".

Practically, I prefer let and var because of autocompletion. Type one letter then tab. Of course, if I could dictate I might prefer something else. I think of it as being more math like rather than PhD. Nothing wrong with borrowing from math.

Obviously you haven't had to maintain code written by mathematicians that prefer to use one letter names for functions and variables among other peculiarities.

Re: Dave Herman’s contributions to Rust

#13
post #11

Earlier quoted context omitted.

Kotlin's version is even better: val & var Super clear. The "let" version smells a lot of "I have a CompSci PhD".

No, not at all. I hate var & val because I never can remember which is which (from Scala, which I never really used a lot). let vs let mut is /clear/ - you can simply not mix them up.

How is it not clear that var is variable?

Re: Dave Herman’s contributions to Rust

#14

The OP mentions in passing that Brendan Eich "was solidly on team Rust" prior to leaving Mozilla, but adds no further details to that intriguing statement. Wouldn't that make Eich the Most Unrecognized Contributor? I don't think his name would be on any commit repo, after all.

I understood that point as relating more to management than technical contribution - that the support of people like Eich was imperative to keep the project funded, and as key supporters left the project became more susceptible to cancellation.

Re: Dave Herman’s contributions to Rust

#16
post #4

Haven’t learned Rust yet. I see they debated this: let and let mut let and var And went with the verbose option. Swift went with the succinct option, which I love about the language. In practice I suppose I do mostly type “let” in Swift so it doesn’t matter much Swift, however, chose ‘func’ instead of ‘fn’, after much debate. Those little things that are debated initially, then forever

In Rust the `mut` does not apply to the `let`, but to the variable binding. So you can do this:

    let (x, mut y) = (5, 10);
After this statement `x` will not be mutable, but `y` will be. You cannot do

    let mut (x, y) = (5, 10);
So the way Rust currently works just doesn't map clearly on `let` and `var`.

Re: Dave Herman’s contributions to Rust

#17
I've heard a lot of engineers complain about engineering managers over the years. I've also heard great managers self-deprecatingly say they "don't do any work". I've seen managers feeling bad they weren't productive so they resorted to writing code to feel that they were having impact.

This post is an example of the incredible impact an engineering manager can have without writing a line of code.

Re: Dave Herman’s contributions to Rust

#18
post #11

Earlier quoted context omitted.

No, not at all. I hate var & val because I never can remember which is which (from Scala, which I never really used a lot). let vs let mut is /clear/ - you can simply not mix them up.

How is it not clear that var is variable?

Yes. I think the problem may be with the other one. "val" (and "let") don't seem obviously constant to me.

Re: Dave Herman’s contributions to Rust

#19
post #15

The same story [0] was posted several hours ago by the author I suppose. [0]: https://news.ycombinator.com/item?id=27016848

Yep, this needs a `dup` mark somewhere.

Edit for down-voters: the typical HN behaviour. Don't be lazy and take a time to explain why you downvote.

Re: Dave Herman’s contributions to Rust

#20
The big takeaway for me is that inside our daily corporate world, we should strive for more open discussion about the work we do - I keep trying to do more discussion-list style work with my team, even though it often is easier to jump on a video call.

It has a payback a long way down the road but my gut knows it is worth it.

Post reply on HN