16 states affected, yet no Canadian provinces, apparently. Good thing smoke can’t cross 5000 miles of open border…

You can always combine integer operations in smaller chunks to simulate something that’s too big to fit in a register. Python even does this transparently for you, so your integers can be as big as you want.

The fundamental problem that led to requiring 64-bit was when we needed to start addressing more than 4 GB of RAM. It’s kind of similar to the problem of the Internet, where 4 billion unique IP addresses falls rather short of what we need. IPv6 has a host of improvements, but the massively improved address space is what gets talked about the most since that’s what is desperately needed.

Going back to RAM though, it’s sort of interesting that at the lowest levels of accessing memory, it is done in chunks that are larger than 8 bits, and that’s been the case for a long time now. CPUs have to provide the illusion that an 8-bit byte is the smallest addressible unit of memory since software would break badly were this not the case, but it’s somewhat amusing to me that we still shouldn’t really need more than 32 bits to address RAM at the lowest levels even with the 16 GB I have in my laptop right now. I’ve worked with 32-bit microcontrollers where the byte size is > 8 bits, and yeah, you can have plenty of addressible memory in there if you wanted.

I know a google engineer who was saying they’re having to update their code bases to handle > 16 exabytes of storage, if you can imagine. But yeah, that’s storage, not RAM.

I watched a documentary on this awhile back. The municipality asked the public if it would be enough for them to dump treated water into a lake and then draw from that lake? And then someone with expertise in the matter commented that this would necessitate another treatment phase, since any wild animal could take a dump in the lake. So he seemed to think closing the loop made the most sense from a practical standpoint.

I think people here tend to question and fact-check posts and comments a lot, which is a healthy thing. Now some say reality skews left, in which case could it be that the right have left because the left is right?

Most recently? My wife was wfh and out of the kindness of my heart I brought her a coke. She was on a zoom call with her entire team. I was pantsless.

literally good for you

I actually asked my family doctor at one point about the health effects of masturbation. She said that as a guy, if you are not otherwise sexually active, it’s good for the prostate to keep the plumbing working down there.

I started in C and switch to C++. It’s easy to think that the latter sort of picked up where the former left off, and that since the advent of C++11, it’s unfathomably further ahead. But C continues to develop and occasionally gets some new feature of its own. One example I can think of is the restrict key word that allows for certain optimizations. Afaik it’s not included in the C++ standard to date, though most compilers support it some non-standard way because of its usefulness. (With Rust, the language design itself obviates the need for such a key word, which is pretty cool.)

Another feature added to C was the ability to initialize a struct with something like FooBar fb = {.foo=1, .bar=2};. I’ve seen modern C code that gives you something close to key word args like in Python using structs. As of C++20, they sort of added this but with the restriction that the named fields have to come in the same order as they were originally defined in the struct, which is a bit annoying.

Over all though, C++ is way ahead of C in almost every respect.

If you want to see something really trippy, though, have a look at all the crazy stuff that’s happened to FORTRAN. Yes, it’s still around and had a major revision in 2018.

I suppose it is a kind of survival training? One of my bandmates who’s served came up after. “So here’s the deal. You watch what everyone else is eating. If they’re meticulously avoiding the peach cobbler or whatever it is, you F’ing stay away from that S if you know what’s good for you!”

I’m in a band that performs on occasion at CFBs (Canadian Forces Bases). We typically eat there and spend the night either in barracks or guest housing.

I have noticed that when we play for officers, dinner is like steak and lobster. When we play for enlisted, it’s more like high school cafeteria. The one and only time I had to excuse myself towards the end of a concert and miss the closing number was after eating at the enlisted mess and getting explosive diarrhea.

Fair, though I guess my interpretation was that void* is kind of like a black hole in that anything can fall into it in an unsettling way that loses information about what it was?

I don’t really have an answer for you, but can say when recompiling older codebases (some in C and some in C++) using a modern C++ compiler, typing errors are among the most common I have to address. In particular, compilers seem to insist more on explicit casts for type narrowing, which is a good thing. But I don’t know about modern C itself? It wouldn’t surprise me if the language has become stricter.

Same in Japanese. araiguma translates as washing bear.