CakeEngine

Maybe they've just not thought about that (yet). It looks to be mostly coded by Claude so, presumably, it been a very quick project to take from zero to where it is now, and they're in the mode of throwing old socks at the wall.

Also in the 80s we (by which I mean other people), downloaded software from the television by sticking an LDR to the screen whilst a dot flashed black and white during the duration of a programme. A program from a programme.

I remember see the dot a few times, but it was probably very short lived.

Is this not something that can be addressed with cameras and (maybe) learnt approaches now? You don't need blind repeatability if you've got good visual monitoring to close the control loop, you just (just!) need good accuracy and low latency from video to motor control.

Another early 90s C learner here, and I also put (and still do!) parentheses around return expressions. But I do:

   `return( 1 );`

not

   `return (1);`

...because the bracket belongs to the return, not the expression. It's by analogy with 'if' and 'while', a mental "look out, here comes an expression" warming.

Indeed. There's also UZI - a v7 UNIX for Z80.

I don't think it would be. You'd have to detect them on the data bus and also differentiate between data and instruction accesses which I don't /think/ the Z80 does, at least not easily.

This is only a problem is there's a clear mapping from detectable genetic feature to an expressed macro-feature like intelligence.

My (admittedly limited) understanding is that each detectable genetic feature has a whole panoply of effects, some of which wont' be apparent at birth. Selecting for intelligence through specific genes is like to also be selecting for weak bones, reduced longevity, or other unpredictable side-effects.

Maybe one day it will be possible but there's a chasm between here and there which can only be crossed by extensive testing on real people. Is that even crossable?

Folk are getting hung up on the keyboard layout and poor buttons, which are bad but only the start of the problems with these machines.

It has two separate asynchronous screens, two sets of printed instructions (plus t&cs), more instructions on both screens, then two keypads (but with the same symbols although they're not interoperable). There is no consistent self-explanatory language for talking about the various buttons, knobs, slots and problems, and how the user's attention should flow between them. If use of this machine wasn't mandated, nobody would ever, ever touch it.