HL33tibCe7

> But I think it's wrong to assume most people are incapable of serious, thorough thinking

I never said otherwise. I said that many are incapable, not most

You’re severely overestimating the mental capacity of a large section of the population.

In fact, almost the entire population after little sleep or on a bad day is likely to make mistakes while following your proposed scheme.

Look forward to this post being flagged

Yes, Your Honor, I did convince this teenager to kill herself - but 150 people a year die from coconuts!

Okay, but if you returned a wrapped error it’d at least be easier to debug.

An unwrap like that in production code on the critical path is very surprising to me.

I haven’t worked in Rust codebases, but I have never worked in a Go codebase where a `panic` in such a location would make it through code review.

Is this normal in Rust?

vlang is pretty much this

It returns the zero value for all types, including arrays (which is nil).

nil is equivalent to the empty array, which is why the rest of the code works as it does.

> But it's not easier at all, and learning curve just moves to another place.

Hard disagree. Go has its sharp corners, but they don’t even approach the complexity of the borrow checker of Rust alone, let alone all of the other complexity of the Rust ecosystem.

The fact that certain specific data centres are being proposed or built in areas with water issues may be bad, but it does not imply that all AI data centres are water guzzling drain holes that are killing Earth, which is the point you were (semi-implicitly) making in the article.

The value prop here is for existing projects in C or C++, as is made abundantly clear in the linked article