Cppcheck doesn't flag anything in Waffle Iron's example.

It also doesn't find anything wrong with:

std::vector<int> vec = {1, 2, 3, 4, 5};
auto it = vec.begin();
vec.push_back(6);
std::cout << *it << std::endl;

Which is another common example of how you can write memory errors without using C++ pointers.

Sure, so C++ is safe as long as it's used in a way that makes it incredibly painful. Sounds good. Let's just require all C++ code everywhere to be written that way. Rust usage will skyrocket overnight.

He unintentionally used Signal? How drunk was he?

For a really rigorous definition of "fair", it's impossible to have fair democracy at all. Arrow's Theorem demonstrates this to a large degree, although many have argued that some of his fairness axioms are excessive. More recent research has concluded that fairness is the wrong standard, because there's no way for an electorate's "will" to really be fairly represented by any electoral system, not in all cases. Some systems can do better most of the time (and "winner take all" is particularly bad), but all systems fail in some cases.

What we need to aim for instead of fairness is "legitimacy", which is more about building broad acceptance of the system than about fixing the system itself, though it's easier to build acceptance for better-designed systems.

Having the country's top politicians continually claiming the system is unfair and rigged is, of course, the worst possible thing to do if you want to build support for the legitimacy of the system.

I decided to check :-)

According to the Book Censorship Database from the Every Library Institute, both "Of Mice and Men" and "Adventures of Huckleberry Finn" have been challenged, but only "Of Mice and Men" was removed, though "restricted" is more accurate. The Birdville Independent School District in Texas removed the book from general access, allowing access only to the AP English class, and the Indian River County Schools in Florida restricted it to high school students.

No Doctor Suess books were banned, although Suess Enterprises voluntarily ceased publication of six books.

ve never seen a software distribution mechanism as careless and sloppy as NPM. Bazillions of dependencies and no signing of packages. [ ... ]

Rust's cargo packaging system is almost exactly the same way. And the last time I looked, Go's packaging was very similar. And package signing won't help if the maintainer's key/cert has been exfiltrated and cracked.

This is what you get when you embrace DLL Hell -- the idea that you should pin your program to a single specific revision of a library, rather than, y'know, doing the engineering work to ensure that, as an app author, you're relying only on documented behavior; and, as a library author, to be responsible for creating backward compatibility for old apps linking to old entry points. Sticking to that principle lets you update shared system libraries with the latest enhancements and bug fixes, while remaining relatively sure none of the old clients will break.

"Sometimes you have to break backward compatibility." Agreed, but the interval between those breaks should be measured in years, not days.

Those bonds will help keep the air conditioning and refrigerator on when a hurricane wipes out electricity for weeks in half your state.

Substitute snowmageddon or heat dome as regionally appropriate.

It's mostly WINE though isn't it? Well, Proton but still. That has the 64bit-32bit thunking layer required. Native Linux builds would need to be 64 bit true, but that's where I was going with the "10-20%" bit.

I run 32bit Windows games on ARM via Rosetta/MacPortingToolkit. So long as the game itself is tricked into believing it's in a 32bit universe, it's happy.

gah - Kinoite. Spelling.

That's chicken and egg though. I use Bazzite, Fedora Kinorate with some gaming tweaks. Fedora wanted to drop 32 bit and there was a lot of noise as things like Bazzite or any gaming usage at all from that distro would break.

But, if Steam went 64 bit then that's 80%-90% of the issue solved straight away, and the last 10-20% would quickly sort themselves out in response. Summary is the distros have already indicated they don't want to do the work, and it's userland that's holding them back right now. Would be mutual benefit to lose them, but userland has to move first.

It's a good thing my Windows 7 game laptop is 64 bit.

Everyone online knows that. The vast majority of the population doesn't - it's not general knowledge outside of people that spend a lot of time online. That where you get this 'the famed hacker 4Chan' or 'CEO of Bitcoin' nonsense in reports, it's simply not their world and they don't swim in these waters.

I mean, I've been online since about 1989 and even I don't know that much about actual 4chan, to me it was always the Lion King's "You must never go there" scene (and then came 8chan - my god).

It doesn't surprise me that those who aren't immersed in this environment daily don't actually know that much about it.

So, how does anyone enter the workforce?

Outside of a very small community (of which I am a member) this won't even register as a problem, let alone motivate a sizeable number of people to do anything about it. Our species lacks the will to even stop literally poisoning ourselves.

Liberals are fairly consistent in defending people's right to their faith while speaking out against people who want to impose their faith on others.