dfox

Note that this list is list of places where if you are enterprise starlink customer SpaceX can provide you with physical ethernet port to plug your cable into when you want to handle your traffic yourself instead of that just going directly to the internet. That is kind of obscure service that even land-based PLMN operators offer but usually do not document in this way in publicly available documentation.

From the perspective of network design, the fact that this certainly is not exhaustive list of places where SpaceX has physical DC presence and physical reality it comes that some of these datacenters are selected based on the fact that the ground station is somewhere nearby (I would be surprised if there is even just one place on the list where nearby means "on the roof", because there is a lot of technical, logistical and administrative reasons why you do not want to put such a thing at a roof of a datacenter).

The "two E10Ks" part is the important part there, as you need a very powerful server to support SunRay users running Solaris. At my university there was something like 200 SunRays supported by cluster of T2000s (7 nodes IIRC), it was fine for CDE, Firefox and few dtterms, completely unusable with Gnome (it took Gnome like 10 minutes to even start).

On the other hand I have heard of some success stories about using SunRays as RDP clients, which is actually supported configuration (you still need a Solaris box that manages the sunrays and translates RDP to ALP).

In washing machine application the locking action is quite fast as the heating element is PTC connected more or less directly to mains, pretty substantial amount of energy gets dumped into the wax over few AC line cycles. In that application (and also in most industrial automation situations) ~100ms is more than fast enough because when most of the effector components are AC powered you end up with ~40ms worst case actuation delay just from the physics of AC electricity. On my washing machine it is quite noticeable that when you press "start" the door gets positively locked well before the capacitive sensing "button" finishes playing its haptic feedback non-sense. (the fact that front panel of cheap-ish toploading washing machine is actually a huge touchpad with haptic feedback that is designed to look and behave like five physical buttons says many things about economics of manufacturing stuff for that somewhat hostile environment at these scales)

You are assuming that the forgers care about the machine readable part at all. Vast majority of forged EU ID cards I have seen are trivially recognizable by the fact that the MRZ contains something that kinda-sorta matches the human readable part, but is syntactically invalid and has wrong checksums.

The problem there is that this is exactly the class of bug that does not exist in GNU coreutils because of philosophy of that project. Non-existence of such bugs proves that the impementation is not copied from AT&T code.

At a first glance passive RFID would be a perfect match for ride photos, the whole mechanism is ridiculously fast so speed of the ride would not matter much (the technology works at highway speeds just fine) and can work over ~15 meters.

But there are two somewhat significant issues with the radio layer in this application: the geometry of tag antenna is somewhat critical (making it into a band would be problematic) and the back scatter is attenuated by salt water blobs (ie. people) almost perfectly.

I suspect that is not an inherent limitation of the dual-ISA design (the HotChips slides mention some sort of bidirectional thread state mapping between arm and z), but just about there not being z/VM release that supports that (building such a thing is probably SMoP, but another question is whether that makes business sense).

IBM's mainframes do not really have a reset vector, the CPU gets initialized by some external means into whatever state the OS expects and then the clock gets enabled, so that distinction is quite moot.

They were always required. IIRC early AMD64 CPUs did not support x87 instructions in long mode at all (causing #UD), and that support was Intel's extension in first EM64T CPUs.

Basically the only thing interesting about the ConcertMaster is that Carmack used it (and that it looks somewhat cool). As for the keyboard itself, it is just a basic OEM membrane keyboard and not that good one even. The speakers are lets say adequate for the time and size.

Interestingly, the speaker part and the keyboard part are completely separate. The "cable" consists of four separate cables (keyboard, power, line out, mic in) in a thin sleeve. Mine was supplied with AT plug on the keyboard cable and Y-adapter that converted PS2 into AT DIN and barell jack for the speaker power. The keyboard label indeed says it is powered by 9V DC, but I guess that never really happened as PS/2 is 5V no matter what various devices say.

Edit: And as for the supper hard to find nowadays part: I suspect that part of the reason is that the keyboard module inside the thing is ridiculously sensitive to even minor spills.

Do not do this unless you do not have any other choice. Preferrably use whatever native barcode support of the printer involved, if it does not have that, just generate the barcode as vector image or bitmap with a resolution that is a integer fraction of the printers resolution. Generating correct Code128 as a SVG is about the same amount of work as generating the correct input for some sort of barcode font (the hard part is determining the switches between character sets, not generating bars from bytes).

The fact that this is standard practice does not mean that it is not perverse. It kind of works sanely for plain Code39 (and even then you will see effects of doing that in weird places, like VAG stamping human readable VIN on a chassis, including the Code39 start/stop symbols), once you start using barcode fonts for Code128-derived symbologies (ie. UPC/EAN) the whole thing becomes a pointless exercise.