5C5C5C

Google is an enormous company which operates flatter than you'd expect for an organization of its size. It's entirely possible that someone from Google was involved in organizing this (i.e. booking the venue) without having buy-in from leadership. Once leadership became aware after being asked about it, they may have shut the whole thing down because they knew the optics would be bad.

Speaking as an annoying Rust user, you're being bigoted. I'm annoying, but the vast majority of Rust users are normal people who you wouldn't even know are using Rust.

Don't lump all the others in with me, they don't deserve that.

How exactly is an individual supposed to determine which cops will be good and which will abuse their power?

Just as we can't make a general statement that all cops are definitely bad, you can't make a general statement that all cops in any particular country or town will be good.

From a basic risk management viewpoint, it doesn't make sense for anyone to accept the risk that any given cop won't abuse their position, even if we were willing to accept that very few would actually do so.

Cops have an extremely privileged status in society and the amount of damage that a bad one can do to an individual - on purpose or even by accident - is incalculable, including setting up an innocent person for capital punishment as we're seeing unfold in Missouri right now.

There have been articles out there for multiple days now which spell out your same conclusion, but these CNN clowns keep pushing the same false narrative. It's blatantly intentional misdirection at this point.

The official act could be to use the national guard to rescue a US citizen from wrongful imprisonment, but that's the kind of thing that racist Republicans would start a civil war over in the name of "states' rights".

You'd be amazed at how resistant most people are to anything that feels unfamiliar, even if it's good for them. Coal and oil jobs are familiar, green jobs are not.

It should be as simple as you're suggesting, but sadly it isn't.

Best practice when using .unwrap() in production code is to put a line of documentation immediately above the use of .unwrap() that describes the safety invariants which allow the unwrap to be safe.

Since code churn could eventually cause those safety invariants to be violated, I think it's not a bad thing for a blunt audit of .unwrap() to bring your attention to those cases and prompt to reevaluate if the invariants are still satisfied.

But only if pattern matching were included, otherwise they would be as unpleasant as C++'s std::variant.

This makes a lot of sense, but the functions were Rust bindings for plain C functions, they weren't function pointers. Granted I could have put pointers to the function bindings into fields in a struct and stored that struct in the mutex, but the ability to anyhow call the bindings would still exist.

It's a massive win, and I would question the credibility of any systems programmer that doesn't recognize that as soon as they understand the wrapper arrangement. I would have to assume that such people are going around making egregious errors in how they're using mutexes in their C-like code, and are the reason Rust is such an important language to roll out everywhere.

The only time I've ever needed a Mutex<()> so far with Rust is when I had to interop with a C library which itself was not thread safe (unprotected use of global variables), so I needed to lock the placeholder mutex each time I called one of the C functions.

I honestly believe the two are related. I think big meat agro business is paying influencers to promote toxic masculinity and push nonsense like "plants emit toxic hormones" on social media.

Valid questions. Do we have firm answers to any of them? And absent firm answers, what kind of risks to the safety of the general public are we willing to accept in service of ideological values?