A good lawyer would get any evidence collected using illegal means quickly tossed. That's not to say the FBI aren't experts in parallel construction, though.
Federal government has different spectrum. Nothing you've said supports the FBI (or whatever gov't agency) transmitting on frequencies assigned for civilian cellular phone use.
If it's not network connected (ntp or gps), or connected to a properly calibrated atomic clock, it's going to be off by more than a second when the next leap second rolls around, anyway.
If you don't need time accurately sync'd to UTC, you can ignore leap seconds, so what's the problem? And if you do need time sync'd to UTC, you will need some regular external input which can include upcoming leap second info, so what's the problem?
"How about instead of setting the time to 23:59:60, the value 23:59:59 happens twice"
So, an event which should run once at 23:59:59 gets run twice? Or if you're logging event sequences, an event which happens later can be logged at an earlier time? I predict big issues with database sync in your future.
When DST happens, there is no duplication of time numbering, the time scale itself changes. 1 AM EDT is not 1 AM EST.
And, before you say you need to know that before you write your code, do you also need to know in advance that "JohnQSmith/aE8&fv84%" might someday be a user's name and password? If you're writing a program which requires deterministic future time intervals, you shouldn't be using the UTC time scale.
What you're suggesting is a variable length second. That's what GMT was before the current UTC came along. The slowdown of Earth's rotation is NOT a known factor, it varies. Things like earthquakes can change the period unpredictably.
Modern UTC ticks at a predictable rate, which is useful for some sciences. Leap seconds keep it in sync with the Earth's rotation, which is useful for others. UTC with leap seconds was deliberately intended to bridge those two needs.
If someone wants a time scale without leap seconds they shouldn't be using UTC, there are others to choose from, such as TAI or GPS.
Feel free to search the FCC ULS database. Come back when you find one. You won't, because much of that spectrum was "sold" to cell carriers for their exclusive use.
It wasn't reporting, and wasn't presented as fact. In journalism, opinion pieces are not referred to as "stories." "Both sides of the issue" would have been a better phrase, but even then letters to the editor are more likely to be published when they correct factual mistakes in reported stories, not present differences of opinion. There are LOTS of WSJ stories with no corresponding letter to the editor published, and you can be sure that just about anything they publish gets some response.
"Nest Will Now Work With Your Door Locks, Light Bulbs and More"
Reminds me of an old joke: Patient: Doctor, will I be able to play piano after the surgery? Dr.: Of course. Patient: That's great, I never could before!
Doesn't matter. The account was not a personal one, but for a small business which no longer exists. There's not even a rock to try and squeeze blood from.
That's nothing. They wanted a fee to close an account, so I just planned to run it close to 0 and let it sit. They'd eventually figure out that mailing monthly statements was costing them money, and close it on their own. So, I used a debit card, but accidentally tried to pay a bit more than was in the account (by $1 or $2). That kicked off some fee (not overdraft, since they declined the transaction), which they promptly took out of the account, making it overdrawn. So, they could overdraw the account, even if I couldn't. Then, they started charging a daily overdraft fee on the account. About a month later, they complained that I somehow owed them hundreds of dollars for the overdraft they themselves created. That was the first notice I received that they were charging me a daily fee. They never got their money.
"Headlights aren't covered under cars warranty anyway."
Bulbs, maybe not. Lamps certainly are, at least for any reasonable warranty. The OP doesn't appear to be from the US, and to be subject to regulations which prohibit changes to some equipment with which the vehicle was originally certified. US FMVSS doesn't apply outside the US, as much as the US would like to think it rules the world.
Finally, at the time rectangular lamps became legal in the US, there were 4 different types of sealed beam headlamps available - 2 and 4 beam systems in both round and rectangular.
I have left too many technical forums because there is no patience for the multitude of posts "I don't know how to this simple task, poor of me, do my job for me"
You do know that you're screwing up everyone's tech support by doing that, don't you? How else is that call center agent going to answer a technical question, unless they can in turn outsource it to the Internet?
Huh? First, the GP is apparently not from the US and second, the US MMWA addresses warranties not regulation of motor vehicles.
(And if you meant that to imply that the MMWA means you can add on any aftermarket piece of crap to a car with no effect on the warranty, you're wrong again.)
The convention is to tip for personal services. That includes not only waitstaff, but bellstaff, barbers even the guys at the full service carwash (you'd be amazed at how much more time they will spend on your car after they get to know you!). You don't tip the bus driver, you do tip the cabdriver.
Do you get a bonus? That's the corporate equivalent of a tip, so perhaps you should refuse.
"It's been Apple's stance that "it just works" by limiting options to a small tested list for as long as I can remember."
Well, no (or you're too young to remember much). A few examples. Macs will readily accept third party drives and memory, one can use third party mice, keyboards and displays. Heck, Apple even supports dual boot on Macs, so you can run a third party OS. There's a whole third party industry build around making accessories for iThings.
Don't try to argue it's so "it just works," that's just ignoring the planned obsolescence built into many iThings.
Slashdot Mirror
A good lawyer would get any evidence collected using illegal means quickly tossed. That's not to say the FBI aren't experts in parallel construction, though.
Federal government has different spectrum. Nothing you've said supports the FBI (or whatever gov't agency) transmitting on frequencies assigned for civilian cellular phone use.
If it's not network connected (ntp or gps), or connected to a properly calibrated atomic clock, it's going to be off by more than a second when the next leap second rolls around, anyway.
If you don't need time accurately sync'd to UTC, you can ignore leap seconds, so what's the problem? And if you do need time sync'd to UTC, you will need some regular external input which can include upcoming leap second info, so what's the problem?
"How about instead of setting the time to 23:59:60, the value 23:59:59 happens twice"
So, an event which should run once at 23:59:59 gets run twice? Or if you're logging event sequences, an event which happens later can be logged at an earlier time? I predict big issues with database sync in your future.
When DST happens, there is no duplication of time numbering, the time scale itself changes. 1 AM EDT is not 1 AM EST.
That's already provided.
And, before you say you need to know that before you write your code, do you also need to know in advance that "JohnQSmith/aE8&fv84%" might someday be a user's name and password? If you're writing a program which requires deterministic future time intervals, you shouldn't be using the UTC time scale.
What you're suggesting is a variable length second. That's what GMT was before the current UTC came along. The slowdown of Earth's rotation is NOT a known factor, it varies. Things like earthquakes can change the period unpredictably.
Modern UTC ticks at a predictable rate, which is useful for some sciences. Leap seconds keep it in sync with the Earth's rotation, which is useful for others. UTC with leap seconds was deliberately intended to bridge those two needs.
If someone wants a time scale without leap seconds they shouldn't be using UTC, there are others to choose from, such as TAI or GPS.
Does all of your code require deterministic knowledge of all future inputs? If so, I can't see how it can provide any real utility.
"Is there a better way of dealing with the need for leap seconds?"
Sure, use/write software which correctly handles time. Leap seconds with their current, well defined behavior, have been around for over 40 years.
If you have software which assumes a minute is always 60 seconds, an hour is always 60, 60 second minutes, etc., you're doing it wrong.
"But how do you know they don't have one?"
Feel free to search the FCC ULS database. Come back when you find one. You won't, because much of that spectrum was "sold" to cell carriers for their exclusive use.
They do, however, require a license to transmit on those frequencies, which they do not have.
Dupe of a story just 5 down.
My ox is being gored!
It wasn't reporting, and wasn't presented as fact. In journalism, opinion pieces are not referred to as "stories." "Both sides of the issue" would have been a better phrase, but even then letters to the editor are more likely to be published when they correct factual mistakes in reported stories, not present differences of opinion. There are LOTS of WSJ stories with no corresponding letter to the editor published, and you can be sure that just about anything they publish gets some response.
"Nest Will Now Work With Your Door Locks, Light Bulbs and More"
Reminds me of an old joke:
Patient: Doctor, will I be able to play piano after the surgery?
Dr.: Of course.
Patient: That's great, I never could before!
Doesn't matter. The account was not a personal one, but for a small business which no longer exists. There's not even a rock to try and squeeze blood from.
It's not a "story." The original was clearly labeled an opinion piece.
That's nothing. They wanted a fee to close an account, so I just planned to run it close to 0 and let it sit. They'd eventually figure out that mailing monthly statements was costing them money, and close it on their own. So, I used a debit card, but accidentally tried to pay a bit more than was in the account (by $1 or $2). That kicked off some fee (not overdraft, since they declined the transaction), which they promptly took out of the account, making it overdrawn. So, they could overdraw the account, even if I couldn't. Then, they started charging a daily overdraft fee on the account. About a month later, they complained that I somehow owed them hundreds of dollars for the overdraft they themselves created. That was the first notice I received that they were charging me a daily fee. They never got their money.
I was thinking more of Subterranean Homesick "the pump don't work 'cause the vandals took the handle" Blues.
"Headlights aren't covered under cars warranty anyway."
Bulbs, maybe not. Lamps certainly are, at least for any reasonable warranty. The OP doesn't appear to be from the US, and to be subject to regulations which prohibit changes to some equipment with which the vehicle was originally certified. US FMVSS doesn't apply outside the US, as much as the US would like to think it rules the world.
Finally, at the time rectangular lamps became legal in the US, there were 4 different types of sealed beam headlamps available - 2 and 4 beam systems in both round and rectangular.
You do know that you're screwing up everyone's tech support by doing that, don't you? How else is that call center agent going to answer a technical question, unless they can in turn outsource it to the Internet?
Huh? First, the GP is apparently not from the US and second, the US MMWA addresses warranties not regulation of motor vehicles.
(And if you meant that to imply that the MMWA means you can add on any aftermarket piece of crap to a car with no effect on the warranty, you're wrong again.)
The convention is to tip for personal services. That includes not only waitstaff, but bellstaff, barbers even the guys at the full service carwash (you'd be amazed at how much more time they will spend on your car after they get to know you!). You don't tip the bus driver, you do tip the cabdriver.
Do you get a bonus? That's the corporate equivalent of a tip, so perhaps you should refuse.
Get bifocals (or a 2nd pair, just for computer use). As you've discovered, progressives have a very small "sweet spot."
"It's been Apple's stance that "it just works" by limiting options to a small tested list for as long as I can remember."
Well, no (or you're too young to remember much). A few examples. Macs will readily accept third party drives and memory, one can use third party mice, keyboards and displays. Heck, Apple even supports dual boot on Macs, so you can run a third party OS. There's a whole third party industry build around making accessories for iThings.
Don't try to argue it's so "it just works," that's just ignoring the planned obsolescence built into many iThings.
"Apple likes to ensure a consistent ecosystem so that all users have as consistent an experience as possible."
That's an odd way of saying they want to ensure consistently high profit margins.
"Apple wants to avoid cases where users blame Apple for sluggish application performance, skipping music/video, bugs, etc"
So, is it the case that if a user experiences any of those things, it's Apple's fault?