mprovost

It's not a VAX that you're physically plugging a terminal into. The remote machine is totally capable of communicating with a newer terminal, it just needs to know how. You're being nice by giving it that information. You can also just install it locally in your home directory (~/.terminfo). (You used to be able to stuff the entire entry into the TERMCAP environment variable and not install anything.)

Every terminfo is custom, to the terminal it applies to. It's just that most entries are 20+ years old and even glacial distros have converged on some version of the database that mostly worked, until the recent resurgence of interest in actually writing new terminal software.

Wuff, Wuff!!

During Covid, the local corner shop in London managed to source some amazing Bulgarian white flour. It must have been high protein, and made the best bread. Once supply chains went back to normal, they went back to British and Canadian flours, and my bread has never been as nice.

Most of Uber's "platform" seemed like pet projects that engineers used to justify promotions, and then were quietly abandoned.

The bowline is great because you can tie it one handed.

I think HP sold their calculator business to this company. I bought the iOS version of the 15C emulator directly from HP many years ago, but the app store changed it to this company.

It looks like almost the same colour of those David Clark headsets which seem to be ubiquitous in airplane cockpits or helicopters. It's even the background of their corporate logo.

The original Mac with 128KB of memory cost $2,495 when Apple released it in 1984. It would be about 3x that in today's money.

> I wonder if, in 20 years, petrol cars will the preserve of the very rich and the very poor.

That's certainly the way it's worked out with horses after petrol cars took over.

The latest terminfo contains a fix for a bug in the VT220 entry from ESR's 1995 version.

Usually RDMA is over a network that is supposed to be lossless, but it does have checksums to detect corruption and recovers with retransmission. Infiniband NICs handle all of that.

FASP uses forward error correction instead of retransmission. So instead of waiting for something not to show up on the other end and sending it again, it calculates parity and transmits slightly more data up front, with enough redundancy that the receiving end is capable of reconstructing any missing bits. This is basically how all storage systems work, not just Weka. You calculate enough parity bits to be able to reconstruct the missing data when a drive fails. The more disks you have, the smaller the parity overhead is. Object storage like S3 does this on a massive scale. With a network transfer you typically only need a few percent, unless it's really lossy like Wifi, in which case standards like 802.11n are doing FEC for you to reduce retransmissions at the TCP layer.