As a developer, this silly cryptography check would be very useful during development phases to avoid signing after each compilation. IMHO, they "just" failed to replace the development code by the production code during delivery. A simple mistake ;-)
I don't see how that would be the case here. Please note that the check is performed by the autoupdate software that ships with Zoom, not by the Zoom app itself.
IMHO (almost layman), takoff catapult is the way to go for energy efficiency of aircraft. If you imagine a takeoff around 200KIAS, the conversion of cynetic energy in potential energy gives you a big part of the climb. The spared energy would increase the flight range.
I work as contractor for EUROCONTROL. 90% of the time, the usual order (Lat/long) is used in software. When this is not the case, it is a good indicator that I need to be careful about the conventions used to represent all data. I have already encountered the reversed wind direction and more frequently the use of m/s instead of knots (for wind speed).
Right, I knew that not all SI units were base ten. But I also knew that lat/lon is in degrees, not radians. I also saw the Wikipedia section that knots are still used in industry rather heavily due to their relation to nautical miles. Also not SI.
I recall that astronomical units are also not SI.
Mentioning computers is just a cheap shot, I admit. Still, is valid.
Cooking is an odd one. The old units that were largely defined in thirds are quite useful. Weight is, of course, more reliable for baking, but you can go very far at home quantities with cups and spoons.
To be fair, I'm a large believer that the units are arbitrary and whatever you learned will be good. Such that if you learned SI, it had advantages off the bat. But I am in less agreement that they have an intrinsic advantage.
Knots and nautical miles are interesting because the nautical mile was originally based on latitude: one minute (1/60 degree) of latitude was 1 nautical mile.
So an airplane traveling due north at 120 knots would cover 2 degrees of latitude per hour.
Most of the US Customary and British Imperial units actually have similar logical definitions or derivations, but they aren't regularly taught anymore.
Right. My point was more that in industries where there is some advantage to keeping a non SI unit, they are want to do so without major external pressure.
So, knots persist because lat lon persists. Home cooks persist with imperial in some places because nobody cares to reprint all recipes and measuring devices. Astrological units because at that scale... Nothing scales. And computers, because binary won. (Curious to consider if ternary had been the winner...)
I confess I am actually personally moved by some of the intuitive arguments for older measurements. Usually very physical based and very in tune with numbers actually used in an industry. It is odd to think of a sixteenth inch wrench, but it is just the natural result of dividing by two, four times, after all. (That is, you have a measuring rod, put a midpoint on there. Four times. Now, do the same for millimeters?). (granted, in the age of computers, any measurement is much easier to do at the machining level.)
A typical case of the governing body decides one thing but in practice the "since-always" used convention is still preferred I guess? At least this is my experience with dealing with reqs from customers within aviation.
As a rule, yes, but not necessarily and not everywhere. The important part is to have a coherent set of units, which usually is going to be SI units, but not always. If the user's preferred unit never is going to be SI, does it make sense to base your program on SI units?
For example, aviation deals heavily in flight levels (multiples of 100 ft). If flight levels are a first-class concept in your program, then you're already using non-SI units below the presentation layer. At this point you've established that some altitudes in your program are expressed in feet, and it might be a better idea to use feet for altitudes everywhere rather than introducing a lot of unit conversions. Or it might not be.
I took it as in the presentation layer, but I can see where you're coming from. In that case I would agree with you, and I'm not sure why GP would complain about that.
IMHO the most important period for microsoft is the 90s. There is nothing about it in this article. 1990 is windows 3.0. In 2000, it was the start of Ballmer's era with the erratic management.
France recycle spent fuel for whole Europe. In order to reuse a part of plutonium, most of the plant consume a mix of uranium and plutonium: mox. AFAIK, France has huge piles of useless plutonium.
