It makes total sense that new C++ will contain a higher percentage of bugs than old C++, but after being an almost full time Rust dev for the last two years, you will not convince me that new Rust code has more bugs than old C++ code.

So far I have yet to come across a bug in any of my Rust code that made it into production. All issue reports from users are still related to the C++ code base that we haven’t managed to fully divorce from.

The only advantage to C++ interop is that managers want to see new code get deployed immediately and continuously. They don’t want to wait until the corporation’s billions (literally) of lines of code are all rewritten in a new language before they start to see the benefits of that transition.

The “reform is impossible” is a self-fulfilling prophesy because it leads leftists to never try to get involved in the party, which means they’ll never get a seat at the table, which means they’ll never be able to steer the party.

I certainly can’t prove that the influence of big money can ever be overcome within the party by grassroots organization, but you also can’t prove that it’s impossible (you can only prove that it’s difficult, which is something I certainly won’t dispute).

You certainly can’t prove that a true socialist movement will ever gain traction in America. It seems like the general public is so brainwashed they would rather be indentured servants of large corporations than lift a single finger to seize the means of production.

So we’re left with two unprovable paths to consider, and here’s the thing: the two paths are not mutually exclusive. Leftists can try both at the same time with neither being disruptive to the other. So this is the pragmatism: consider all possibilities and put the eggs into more than one basket.

Or he’s a pragmatist who is concerned with both harm reduction and the likely reality that the only takeaway that Democrats will ever have from losing an election to someone right wing is that Democrats need to go even further to the right to win.

If leftists give the impression that nothing will ever be good enough for them then

1. Democrats have no incentive to court the left
2. Democrats have no estimate for how many votes they would even be able to pick up from the left relative to how far left they might try to reach

I personally believe that if the Democrats had taken on a progressive populist anti-genocide platform they would have won the election handsomely, but I am left with no way to empirically prove that to anyone because so many leftists opt out of voting entirely.

She would have lost Michigan and Wisconsin by even larger margins if she went with Shapiro instead of Walz.

That sounds like it would tickle.

I’m not convinced he really believes that OpenAI is going to roll out AGI in the next ten years, but I’m completely sure he’s determined that it’s a good marketing strategy to make people believe that he believes it.

These graphs only cover the demographic of 18-29 year olds, which historically do lean heavily towards progressive.

OP really needs to heed this advice. Modifying things in the cache will cause breakages that will confuse the hell out of you.

Calculus was invented in the late 1600s, almost 2000 years after the Roman aqueducts were built. The Roman engineer would know some geometry, but certainly not calculus.

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.