This doesn't sound like something Kennedy would do. You do know he provoked the Cuban Missile Crisis and was ultimately the one who committed the United States into Vietnam, right? A lot of people like to pin that on either Johnson or Nixon, but it was in fact Kennedy who ordered boots on the ground and ordered the CIA to manipulate local elections, the overthrow oh the government it originally put into place, ultimately leading to the assassination of Ngo Dinh Diem.

Either way, there's no way in hell the USSR would have done that. Even if Khrushchev was somehow on board, good luck selling that to the Russian politburo at the time in that pretend union of republics: The prevailing sentiment among Americans and the soviets alike was that the US was losing the cold war, even though in retrospect neither the US nor Russia had any idea just how poorly Russia's economy was doing. Either way, why would they give up their lead while everybody thinks they're ahead just to get better gains later? That would be very un-Russian, even today, and you know it.

... have we accomplished their foremost tasks first?? Priorities, people!

https://www.space.com/8725-nasa-chief-bolden-muslim-remark-al-jazeera-stir.html

You (and the slashdotgeist) would love this if there were a D involved. But carry on ...

The point, for the comprehension challenged, is that public school kids are literally monitored by the government all day, not just on the bus.

True, but enough about Iran.

I'll just leave this here.

https://www.youtube.com/watch?...

If you're going to shit on a language, do it to C++. C developers, even if they don't use rust, typically understand why it exists and why it's needed, even where they see C++ as being a worse than useless dumpster fire.

C++ developers usually hate C developers because C developers don't buy into the same crap that C++ does. C++ developers hate rust because it completely outclasses their language in Every. Single. Way. without anywhere near the complexity. They inevitably fall back into the "the world needs C++ because legacy code!" argument, yet they also contradict themselves by denying that they're currently sitting where COBOL was in the 00s, or that C++ looks to C and Rust developers like COBOL looks to C++ developers: Quaint and overengineered.

Hmm...that hasn't been my experience in rust since at least 2023. I don't recall exactly when, but the borrow checker got a lot smarter about this kind of thing, particularly being able to tell whether you're borrowing again while still borrowed within the same scope. At the very least, mutable refs, like all references with a non-static lifetime, only live as long as the declaring scope of the variable holding them, never longer. That scope can be a function, but it can also be much narrower, i.e. within just *any* set of curly brackets. Was the &mut dropped by the end of the scope within that match block? If not explicitly so, i.e. the scope lifetime of the &mut isn't entirely within a set of curly brackets, and the variable isn't ever used outside of that, if a variable is holding the &mut to begin with. If not, try assigning that &mut to a variable, then drop() it after just to see. If nothing else, the compiler will tell you and even visually show you exactly where it's being used.

I abused the borrow checker pretty good here, still compiles: https://play.rust-lang.org/?ve...

Yeah, but the posting said, for Linux, "We are using RDRAND, but it is being mixed in with other entropy being gathered from the system"

If you gather entropy from the environment, like noise from certain chips, start ms time since some last connection, keyboard/mouse movements, etc, that, alone, is random enough for most any use case. And since they are applying that on top of any hardware random number generator, it ensures that it is even MORE random and prevents hardware companies from cheating.

They think center-left is ultra right-wing.

Some mostly sensible people consider themselves center-left and feel hurt that the he Valley types are calling them fascists.

It's all complicated by the 1D spectrum model of the French Parliament being applied to politics broadly.

The Left Authoritarians really hate the Right Authoritarians while the Left Libertarians and the Right Libertarians mostly get along.

It sort of makes sense becauae violence is inherent in the former while cooperation is inherent in the latter.

But the angry aren't usually educated im polisci at all and just operate on the Friend/Eny distinction of their tribe's momentary collective preferences, which can turn on a dime.

The Valley oligarchs will also switch allegiances instantaneously if they perceive advantage in profit or control with shifting winds.

They keep adding timing noise to these API's as attacks show up but this really speaks to the need to have the noise in the core I/O libraries, not inside each new API.

If it's writing to disk in any way it should go through a code path with timing noise.

It would be easier on the feature developers too.

Probably in the network API's too. Have a turbo mode in preferences at one end of a privacy slider, maybe. Default should be safe but the browser benchmark people incentivize the wrong thing. "You get what you measure" and stuff.

It's an overseas market too.

Lots of defects in the case.

Somebody said his legal defense is that if Congress can do it he can. If true it could be an impactful case.

Have you used the map.entry(&T) methods? i.e. or_insert, or_default, etc. Basically, if the entry isn't already initialized, it does so, then yields either what you specified to insert, or the default. Those ended up solving all of my borrow checker issues with hashmaps. A lesson I learned very early in my rust days:

https://stackoverflow.com/ques...

They also make it much easier to to deal with the "vector inside of each hashmap entry needs to be initialized" situation a hell of a lot easier than you've ever done it in any other language before. An interesting side effect of the borrow checker is the rust developers got a strong desire to make the language ergonomic, and this was a badly needed pattern in every language that you never knew you wanted.

The borrow checker keeps paying insane dividends. It was built for memory safety, but gave us incredibly easy concurrency and parallelism, and stuff like this. This is why I keep telling people that the memory safety aspect of rust is merely the cherry on top, the main course of the meal is making doing things the right way the easy way.

In theory, it can, but in the real world it just doesn't. Rust aimed for C++ level performance, but ended up being within a hair of C in real world situations. C is the benchmark because it's generally the fastest high level programming language aside from fortran, though C saw broad adoption that fortran did not, basically because of Unix, with C being used to make (previously assembly) Unix portable to more hardware architectures. C++ came around at a time when fully object oriented programming seemed like a good idea, even though inheritance later proved to be a terrible idea, and to fix some problems with inheritance, C++ added...multiple inheritance...which turned out to be an even worse idea.

Yep; lots of people use this stuff.

This is just random self-preening going on here.

When I was a kid, it was people who would brag about not owning a TV or supposedly never watching one. Sure were a lot of TVs around for something nobody ever used though, lol