Which one of those guys was you?!
I would have loved been the director, but... much to my chagrin I wasn't involved with it all.
BTW, Ouachita County, Arkansas is the home of the <Arkansas Law Enforcement Training Academy>,
probably the actual location for this "disaster".
'Interesting' institution/authority.
I'm impressed (even though no macOS [note new designation protocol] software was used)!
Probably like I was by the Mac and its ease of use when I acquired it compared
to what I previously was used to at work produced in Redmond ...
"There is something fishy in the Pacific Northwest, but it ain't Salmon"
Well, every system has its pros and cons.
However, the credulity of the video is stretched a bit by the claim that
"no animals" were harmed, despite Blaze, Sparky, and Little Smokey 'returning'
to their aquarium. I find it extremely hard to believe that those fish were not
harmed by having such horrible 'puny' names!!!
No objections, nothing to add on my part.
Glad we seem to share the same kind of humour.
Obviously, HP has no concern for the mental cruelty to Animalia: Chordata: Pisces!!
Excellent biological classification, xairbus !
But then, HP has no concern for the mental cruelty to mankind either
given parts of their portfolio...
Enjoyed the read on "why VMS chooses to treat the year 2000 as a leap year."
Best and most detailed explanation I've seen, so far.
I absolutely do agree. DIGITAL always delivered substantiated answers
to customer/user requests/complaints.
In another answer they explain why OpenVMS regards November 17, 1858 as
the beginning of time:
The modified Julian date adopted by SAO (Smithsonian
Astrophysical Observatory) for satellite tracking is Julian Day
2400000, which turns out to be November 17, 1858.
SAO started tracking satellites with an 8K (nonvirtual) 36-bit
IBM 704 in 1957 when Sputnik went into orbit. The Julian
day was 2435839 on January 1, 1957. This is 11225377 octal,
which was too big to fit into an 18-bit field. With only 8K
of memory, the 14 bits left over by keeping the Julian date
in its own 36-bit word would have been wasted. They also
needed the fraction of the current day (for which 18 bits gave
enough accuracy), so it was decided to keep the number of
days in the left 18 bits and the fraction of a day in the right
18 bits of one word.
Eighteen bits allows the truncated Julian day (the SAO day)
to grow as large as 262143, which from November 17, 1858,
allowed for 7 centuries. Possibly, the date could only grow as
large as 131071 (using 17 bits), but this still covers 3 centuries
and leaves the possibility of representing negative time. The
1858 date preceded the oldest star catalogue in use at SAO,
which also avoided having to use negative time in any of the
satellite tracking calculations.
Seconds from the Epoch?
That is the UNIX standard and because of that we will have yet another Y2K mess in 2032.
2032 ? Sure ?
I'd tend to believe it's 2038, since the Unix Epoch is a 32- or 64-bit value
(long-/quadword, eventually unsigned; best as time_t) containing the number of
seconds since 01-JAN-1970 00:00, UTC. When interpreted as signed and unsigned
longword values, the upper bound for the C epoch is 19-Jan-2038 03:14:07 GMT or
7-Feb-2106 06:28:15 GMT, respectively.
Time on VMS is a 64-bit (quadword, eight-byte, little-endian) value
containing the numbers of 100 nanosecond intervals since 17-NOV-1858 00:00 (local).
This value is updated every 1/100 sec and its usage is common across the VAX,
Alpha and I64 Integrity Itanium platforms.
This quadword format works up through 31-Jul-31086 02:48:05.47 GMT.
But what is the year 31086 worth if the command line interface/interpreter
only can cope with 4 digits for the year ?
Well, I guess engineering will take care of that in about 7975 years
Regards !
Michel