Posted on 06/16/2017 8:13:43 AM PDT by SeekAndFind
What’s next? Are we going to stop supporting the Cuban army?
.
Neither requirement is complied with.
.
The paperwork quagmire is a particularly putrid area of the swamp. I wonder how many swamp employees dwell there. And how many of those jobs will be cut.
Expect mudslinging.
>
Where is all this paperwork stored?
He showed a 70-pound, $21 Million report that was prepared for one stupid 18 mile stretch of road. Where does that go?
NO ONE could ever read that.
>
Come now, we ALL know that wasn’t to be read, consulted nor followed. It was a make-work project for some govt side-partner/family member/etc.
I mean, it’s not like YOU needed that $$ anyway, right? /s
You betcha. Maybe I'll up my screen name to all caps.
No, but there is the Year 2038 problem
I still live with the y2k bug.
I have some programs that I no longer have the source code to.
So to run them I have to set my p.c. clock back to 1999 and xeq them. They run fine after they start with the clock in 2017.
btw
>
We desperately need a sundown amendment to the constitution for every act of congress, or executive order, terminating them after four years, and requiring the burning of the written copies thereof to generate electricity.
>
You forgot any/all ‘rules and regulations’ which, IMO, should be required to be voted upon and approved by Congress. Else, they are deemed advisory ONLY and can never be used against any entity in court.
There is *NO* authority for Congress to relinquish its Law making authority to any nameless, unelected bureaucracy. To give them ‘force of Law’ w/o Congressional vote is/was an unconstitutional power-grab (and happily rubber-stamped as valid by all).
LOL, might be time for a rewrite.
I’ve always said government bureaucracies are like perpetual motion machines, they primarily exist to go through the motions of keeping themselves in existence.
And if programmers go back to lazy 2 digit years the next problem will be 2100. Because of the catchy name people think the problem was the 1 turning to a 2, it wasn’t, it was the 9 turning to a 0, and 0 turning to 1 can do the same thing if the coders of the mid century aren’t smart.
Winning 17 years after the fact...
I tested my computer and it is Y3K ready as are most computers. However it is not Y10K ready and I am willing to bet virtually no computers are. That means we need to immediately start a program for Y10K readiness at all levels in our government. Just because it is further away in time than the start of recorded history doesn’t mean it is unimportant. This is series.
It’s enough to make a strong man weep.
It prompted me to go look up some stuff on wikipedia about time handling ... which led me to articles about the Y2k38 problem. (Hopefully I don't have to worry much about this one, as I'll be 73 years old, and hopefully either dead or not working on computers any more). ... Which led me to looking at a page about Unix time ... which led me to the following:
At 15:30:08 UTC on Sunday, 4 December 292,277,026,596,[22][23] 64-bit versions of the Unix time stamp would cease to work, as it will overflow the largest value that can be held in a signed 64-bit number. This is nearly 22 times the estimated current age of the universe, which is 1.37×1010 years (13.7 billion), and according to scientists[according to whom?], by this time it is possible all Earth-based systems running on 64-bit UNIX time may be long gone.[citation needed]
I laughed out loud at that last "citation needed", in response to the assumption that by the year 292,277,026,596, 64-bit UNIX systems might be long gone.
The 2038 issue is something that we need to be thinking about, as a lot of embedded devices run 32-bit Linux. Hopefully by then, most of that will have been retired, but it's something to keep in mind. More stuff went on during the Y2K event than was generally admitted to.
But shouldn’t we be preparing now for Y3K?
Actually, the year 3000 isn't really an issue, but 2038 (on 32-bit unix computers) is an actual issue. There are also folks already thinking about the year 10K problem as well.
Also see RFC2550 for some light reading.
I work in computer networks.. and in the late 90’ worked in a NOC (Network Operation Control) for a global Connectivity provider for International Business
Our company decided 2 years before Y2K that "All" NOC Personnel had work that New Year's Eve "just in case" However I had put in a request for Vacation New Year 2000 three years before and had it approved... so there was a big stink but I got Y2K night off
I scheduled my Y2K vacation about 7 years in advance. (Mentioned it in my job interview) I was the only one off as well.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.