nessus42

OTOH, for my development Mac, I have 64GB of RAM. (Though 32GB would probably be fine.)

Wow, that's dedication!

I wrote my own adventure game for my Commodore PET, which had 8K of RAM. It worked well, but after three rooms of content, I ran out of RAM, so then I gave up.

Wow, that sucks!

When I was a kid, I had an 8k Commodore PET. I wrote a text adventure game for it, but I ran out of RAM after implementing the parser, inventory, and three rooms.

Well, it worked, but there wasn't much to do, other than follow the Wumpus around....

On the other hand, Bohm's interpretation seems pretty ad hoc. And it also includes all of the other worlds that MWI has in it via the pilot waves that continue to exist and propagate forever. (The pilot waves never collapse.) It's just that only one of those many worlds ends up being "real".

It worked perfectly! Until a stewardess caught me and made me stop.

He mostly switched at some point to betting on sports. He arbitraged the odds that the bookies used compared to odds that were apparently more accurate, probabilistically.

I asked him how he could possibly have a better sense of the probabilities than the bookies, whose job it is to get this right. He replied that the bookies don't set the odds based on probabilities, but rather just so that they have an equal amount of money on both possible outcomes, and therefore they would always make money no matter what.

So the odds that the bookies used were often not good measures of the actually probabilities, but rather often more a measure of public sentiment. And he could take advantage of this difference.

Working at a university, no one would pay for me to have a time domain reflectometer (aka TDR), which would have helped determine if there was a bad spot in the Ethernet cable somewhere.

One of the assistant directors of the lab told me that I didn't need a TDR, because I could just diagnose the problem with a signal generator and an oscilloscope. (Which is what a TDR basically is, but just bundled up to be convenient to use.) I ended up doing just that, and was able to determine that there was a reflection happening on that section of Ethernet cable, but IIRC, narrowing down the location relied on me having more knowledge than I had about the speed of light in an RG-58 cable. And also, wheeling around a working with the oscilloscope was a PITA.

Eventually I found someone to loan me a real TDR, and was able to determine how far down the cable the problem was occurring. Of course, even with that knowledge, determining where the problem was occurring was a challenge, since the cable snaked in a out of everyone's offices.

I followed the cable, applying the TDR at various points, until I got close to where the reflection was occurring, and it seemed to be occurring where the cable ran through the ceiling for a while.

I should note that all while I'm doing this, people are griping heavily, since it required disconnecting that section of Ethernet, meaning that people couldn't get their work done.

In any case, I got a ladder, pried up some ceiling tiles, looked up into the ceiling, and found a section of the Ethernet cable that had been spliced. At first I figured that one of the splices was bad, but eventually I noticed that the cable that had been spliced in was RG-59.

In case you don't already know, RG-58 and RG-59 look almost identical to each other. IIRC, the only real way to tell the difference was by reading the print on the cable.

Whoever spliced in that piece of cable should be drawn and quartered, but once I replaced that bit of cable with RG-58, everything then worked fine from then on, with no more intermittent outages.

E.g., it's about 20x as fast as InvokeAI, which doesn't have an FP16 option that works on a Mac.