I have a condition so I have a colonoscopy every year. Once I had found out about there being a fast-acting option, I've always chosen that.

I've never done it sedated. I prefer to watch the screen and and ask questions. I've found the view quite fascinating, actually. The doctors and nurses have always been professional, focused on the colon: not the butt. There is absolutely nothing sexual about it. I've never felt pain: only some tension, and that's been because of gas (needed to get a clear view). It is perfectly safe unless your colon has some illness of some sort. The worst part has always been the prep.

Each `jmp` to f0..fX is an optimisation of a `call` and a `ret`, and probably done in a separate pass after the switch-case code has already been expanded.

The `mov edi, esi` at the top of the function is also an optimisation, most likely done during the register allocation pass. This was only possible because all functions take the same value in the same register. Otherwise, there would probably have been also a `mov` before each of the calls.

... unless the size of immediate parameters would have affected code size. In the example code however, all constants fit in an `imm8` parameter to `cmp`.

Having aging eyes, I wish monospace fonts made 8 and 0 (zero) more different from each other. I notice that I have started to confuse those two glyphs when in small sizes.

The DSP was a difference though, for raw calculations. I think it might have been NeXT machines that had started the trend of having a DSP. Commodore had built a prototype of the Amiga 3000 with a DSP in it which was talked about at the time but it was never released. Amiga enthusiasts have only recreated DSP boards in more recent years.

The smallest terminal you can connect to a AAA battery is the same diameter as 00 AWG copper wire.

Provided that the engine has 100% efficiency and can turn 176MW of electricity into torque, to safely run power it needs through that 00 AWG wire, the battery would need to provide a voltage of at least 70 kV.

I still think that reference counting is promising though. First because it meshes well with static analysis memory-management techniques such as inference of uniqueness and borrowing -- that can optimise away RC altogether. (and Swift's compiler already does some of that). I have not seen any work that could optimise away tracing GC in a similar way. Second, because I believe that it would be possible to design hardware with object-memory addressing that would performs atomic reference counting with no additional runtime cost.

Unfortunately, gross negligence -- which you could argue to be the case here -- is often not enough, unless you could show that it has caused real harm.

From my perspective, it is only a matter of time before it is: and that's why there is need for better legislation covering what AI models do.

If you wanted to play games on an Amiga or an Atari ST you needed to use a TV-signal compatible 15kHz monitor or a Multisync monitor. I ran desktop programs in 640×200 mode with four colours on both my ST and my Amiga 500 before I upgraded.

There were also "flicker fixer" add-ons for the Amiga, converting the interlaced modes to VGA signals: one was built into the Amiga 3000.

Macintosh keyboard layouts tend to have many symbols on Option-combinations but they are not always printed.

I think optics could be used to make each camera see a different image.

A video could show shake, which could be verified against readings from the phone's accelerometer -- but you could just hold it still and claim that it was on a tripod.