The individual electron just behaves randomly in a way that we can only predict statistically and not absolutely.

That’s the non-boring part, for lack of a better expression. Quantum Mechanics only predicts the outcome for an ensemble, and that imperfectly. It can say nothing at all about the outcome for a single particle.

Why? Prosecutors dogged Clinton for 8 years.

Congress definitely can and should ban him from office but obviously won’t.

An a380 is so big when it takes off it looks like it’s moving slow, just kind of hanging in the air

Thanks I used to know that one but forgot it.

The wicked flee when none persueth.

That’s not a bad idea.

My uncle told me he sailed through the Bermuda Triangle all the time. I thought he was full of crap.

I use a chainsaw maybe two hours a year. Same with my neighbors, yet each of us owns a chainsaw.

They should have just made more trash robots.

Maybe she really worked at Carl’s Jr.

Scare them with a threat of Medicare cuts.

The first rule of the road is “right-of-way won’t help you when you’re dead”.

“Lefty Loosey righty tighty”

One arrow points up to the left, one points down to the left.

Z

Musk is the E.T. of public figures.

Thanks, I’ve save your comment. I haven’t heard of any of these.

It also has real type safety and thread safety.

Do tell.

Here’s some of my personal complaints. I don’t in general know how to fix them.

1. proc_macros need their own crate

2. generics cause problems. Many useful macros can’t handle them. Try using a generic that’s a complex async function, then pass a closure to it.

3. There’s this kind of weird mismatch where sometimes you want an enum wrapping various types, and in others generics. I find my data flows switching back and forth.

4. async in rust is actually really good, but go does it better. I don’t think rust could match go without becoming a different language.

5. Traits are just a big mess. Trait implementations with generics have to be mutually exclusive, but there aren’t any good tools to make them so. The orphaned trait rule is necessary to keep the language sane but is incredibly restricting. Just today I find certain a attribute macros for impls that doesn’t work on trait impls. I guess I have to write wrappers for every trait method.

6. The “new type” pattern. Ugh. Just make something like a type alias that creates a distinct type. This one’s probably easy to fix.

7. Cargo is truly great, but it’s a mystery to me right now how I’m going to get it to work with certain packaging systems.

To me, Rust is a bunch of great pieces that don’t fit together well.