Re: Wireless Mice
550 posts • joined 23 Sep 2010
When I need either more than about 32GB of mass storage, or I'm concerned about I/O access speed, I run my Pi4s with an attached SSD.
For ones operating below those constraints, I'm using A1 class uSD cards. What I was hoping for from Optane (based on the early claims for it) was not the better speed, though that's not bad to get, but greatly increased number of times you can write to any given cell. Simply put, SD cards wear out relatively quickly if they are being actively used. Longer endurance in use as a root file system would be a desirable trait.
I wrote a COBOL program on an IBM mainframe that needed to extend a record in a VSAM KSDS spanned dataset. That's a valid operation (just read the VSAM manual), but it didn't work. I couldn't figure out why not. The systems programmers in our shop couldn't figure it out. The local IBM support folks couldn't figure it out.
So it go sent to the VSAM development group in (IIRC) the Netherlands. About 6 months later, we got a reply. While what I was doing was valid in VSAM, the COBOL compiler didn't implement it. So they were going to change the COBOL manual to say You Can't Do That.
(IIRC, my solution was to read the record, delete it from the dataset, build a new record with the same key, and add that to the dataset.)
I'm still using Win 7. I'm *considering* building a Win 10 system, but only because it'd be very hard to get a copy of Win 7 and I'm going to be forced to use at least Win 10 at some point, so a low usage machine to get used to it on will be of some benefit. Doesn't mean that I *want* Win 10, let alone Win 11.
Do you correct for locality? For any area controlled by England, the Julian to Gregorian calendar switch took place in 1752. Various other countries made the switch as late as 1923. The Orthodox churches still haven't converted.
Those sorts of problems usually went the other way by thinking that all "00" years are leap years. It's true for the Julian calendar but not for the Gregorian.
I went around three times with a programmer that wrote a new set of standard date routines at a company I worked at. On the first pass, 1900 was a leap year. On the second pass, 2000 wasn't. The third try got it right.
One of my favorite trivia questions is: Could someone have been born on 29 Feb. 1900? It takes an additional bit of data to answer correctly. You have to know *where* they were born, but many, many people don't know that.
One wonders what effect shifting to these slower, less capable, chips will have on Russian military hardware. What, for instance, does the yet to be mass produced T-14 Armata tank really need? All of this especially in light of their obvious need to replace a lot of--at least nominally--"smart" munitions that have been expended flattening Ukraine.
I once logged an error message in a program where it should not have been possible to get to. The message was "Committing seppuku! Arrrgggghhhhh!" followed by the program terminating. One of my fellow programmers on the team managed (somehow) to trigger it. He came to my desk, looked accusingly at me and said, "You wrote this, didn't you?" I had to allow as how I had, so we went over the code together to figure out how he'd managed to trigger the message.
Pirating copyrighted material? USSR did that for decades. The main thing that stopped the practice was the realization that by joining the international copyright union, they could prevent Russian works they didn't want others to read from being published outside the country.
I think you mean WW1. The only biplanes in use in WW2 (that I know of) were the Fairey Swordfish (famed for its part in sinking the Bismark) and some Italian biplane fighters, with a top speed about 250MPH. Apparently Hurricane and Spitfire pilots were a bit embarrassed to admit when they shot one down. (Though at that, they were faster than Ju-87 Stukas, which flew about about 190MPH.)
An amateur programmer writes the code to use himself. (Knowing what the inputs are supposed to be.)
A professional programmer writes the code for other people to use. (Knowing that random users will put in just about anything and having to deal with it.)
Biting the hand that feeds IT © 1998–2022