On early bit-paired keyboards with parallel 7-bit outputs, possibly going back to mechanical teletypes, I think holding Control literally tied the upper two bits to zero. (citation needed)
Also explains why there is no difference between Ctrl-x and Ctrl-Shift-x.
Battlezone and later 3D games used different circuitry that generated vectors with analog circuitry and used a “math box” coprocessor based on Am2901 bit slice ALUs to help with the 3D math.
Growing up in New England at the time, I was very lucky that they ran a pilot project at my elementary school. We programmed our "sketches" (though we didn't use this term) in LogoWriter on Mac LC IIs and flashed them using a weird dongle that connected to the brick via RJ11 cable.
I owe a lot to my teachers and Fred Martin's group. I don't think I'd be a developer today without that experience.
I was fortunate enough to get LEGO Mindstorms (the OG one) for Christmas as a kid. By that time I'd already learned a bit of QBasic and so had programming experience. While I found the visual programming paradigm limiting I also wasn't creative enough to come up with robots that needed more than what one could build with the software so I had no complaints. I had a great time learning about gear ratios and how flaky the light sensor was depending upon room brightness.
Is there anything similar and as well-supported from Lego or otherwise these days? An ESP32 is great fun but some assembly is required.
I was very surprised that GCC could optimize NEON SIMD intrinsics. After spending hours trying to optimize my vector code, trying to get the spacing between register dependencies right to reduce stalls, breaking long reduction operations into intermediate results, messing with LLVM-MCA, etc., I realized that I just couldn’t beat the compiler. It was doing its best to allocate registers and reorder instructions to keep the pipeline filled.
I don’t think it always did the best job and saw a bunch of register spills I thought were unnecessary, but I couldn’t justify the time and effort to do it in assembly…
Storage tubes are amazing. I once had a Tektronix 464 scope. Unlike the ubiquitous 465, the 464 was an analog storage oscilloscope! The persistence of the storage tube let you capture pulses, visualize signal jitter, etc. And there was a very satisfying erase button that cleared the tube with the characteristic green flash.
You could also just mess with the horizontal/vertical position knobs and use it as a very expensive Etch-a-Sketch.
Unlike a television CRT, the storage tube will "remember" everywhere the electron beam struck the screen as long as the voltage is below the erase threshold.
What's wild is that this information can be read back out of the device. So, it's not just a display but also memory. It's a destructive reading process (not unlike core memory) where detection is also erasure, but it really is RAM... of a sort.
I have seen these throughout the US and Europe and been fascinated by them. Penn Station has (had? been a while) a big one with more segments per character. I’ve been trying forever to find the name of this particular style of segmented displays and get more info on them. The closest I could find is “mosaic display.”
Love this article!
Signed,
someone who has an obsession with segmented displays
The Penn Station passenger display was, according to the NYT, segmented LCD glass made by Signature Technologies in Arizona.
It had 43 segments (each character had a 13 segment column, 17 segments column, then another 13 segment column that was a mirror of the first). You can see the segment shape on the original sign:
I've done small embedded Linux systems and it makes me so happy that there is a (mostly) compatible implementation built into busybox. svlogd's rotation and size capping makes it great when using limited-lifespan nonvolatile storage like eMMC.
I do the same thing, although as "embedded" systems get bigger I've moved some things over to systemd.
It's a little complicated to set up if your root file system is read-only, since runit really wants to write to the disk, and you must set up symlinks pointing to tmpfs.
I acquired a nonfunctional Diehl VSR a while back, naïvely thinking I could bring it back to life.
Oh my goodness, I took the cover off and what I saw was jaw-dropping. Thousands, possibly tens of thousands, of the most densely packed metal levers and cams and gears one could ever imagine. Nearly all of which would have needed cleaning and lubrication. Getting this thing fully working could have taken a year or more, especially with no repair manuals, and all available information in German.
The respect I have for the designers of these machines, and the servicepeople who repaired them, is immeasurable.
They are also electrical death traps. Lots of exposed switch contacts carrying mains voltage.
I was there when we added it to Preview ;) I think Nils wrote the code to hook it up, because he also worked on the loupe and how it would automatically lock onto the bounding box of a line.
Hi, Matt. Yeah, one of the engineers is on HN from time to time — I thought he might see the post and respond. (Your reminding me of Nils made me smile this morning.)
Ahem. Actually what I am most proud of is that I made pinch to zoom keep characters focussed during zooming. At that time, Safari let things get blurry until the user stopped zooming and then it snapped to focus. That is what I was supposed to do, but I decided to use mipmaps instead.
Also explains why there is no difference between Ctrl-x and Ctrl-Shift-x.