They drove a wedge into Flash. They're forcing web site designer to accommodate people without Flash. That's fucking awesome. Without the iPhone we would have even more sites requiring Flash, and there would be even less competitive incentive for Adobe to improve their terrible plugin.
So yeah, the worldwide Web would suck a lot more if Steve Jobs didn't have that foresight.
And btw, 50% of what makes the iPad great is the battery life. 10h in full use. Imagine if they had flash, people would have no idea why suddenly their battery is draining down. They would blame Apple, because that's what it says on the can.
He cries on TV while drawing absurd diagrams on a blackboard.
If he's not nuts, he plays one on TV pretty convincingly.
He once called a woman on his radio show to harass her by making fun of her for having had a miscarriage. Among other things. He's nuts, he's evil, he's religious. The word for it is spelled c-o-n-s-e-r-v-a-t-i-v-e.
He's completely insane. He fucking cries on TV for nothing. And he's obviously the type of people who would have supported Hitler or any kind of authoritarian leader.
Time (and TAI) is independent of time zones. Time zones are a way of displaying time. Just like 10 in base 8 mean 8 in base 10, but represent the same number.
And TAI does not have to be calculated, except in as much as it's transmitted indirectly in NTP (which transports UTC and the difference with TAI), because that's where all official time references are derived from.
Why are they not? Leap seconds should not be part of the time source, they should be in the display, just like when displaying local time from a UTC clock. Trying to smooth out leap seconds is of the utmost braindeadness.
The most accurate measurement of what though? elapsed time or time of day?
It's trivial to derive time of day from an accurate absolute clock. It's about as hard as displaying a calendar, i.e. not that hard.
On the other hand it's impossible to derive an accurate clock from an inaccurate calendar clock.
The big problem is that leap seconds aren't predictable so it's not possible to convert accurately between TAI and UTC for a time in the future nor is it possible for a system that isn't receiving updates to the conversion table to covert accurately for past/current time.
It's about as difficult as fetching a file over the internet, i.e. trivial. And if you can't fetch that damn file, the only thing you risk is at most a couple second offset when/displaying/. Your calculations are going to be fine; and missing one second on an interval is a big deal (esp. if you're measuring intervals on the order of 1s), while having an offset on a/date/ is hardly ever an issue. And anyway, as soon as you get back to civilization, and assuming you stored your dates in TAI, you can see them accurately in UTC retroactively.
It follows that if a time is repeatedly converted between TAI and UTC by systems in different states of updating (as could easilly happen in a situation where a gradual migration from UTC to TAI is in progress) there could be some rather nasty error buildups. Much the same problem applies with DST but at least most developed countries tend to keep thier DST rules pretty consistent
That doesn't strike me as a very common situation. Calculating time intervals, on the other hand, is a very common task. See time(1).
There's a reason why the second is defined based on an atomic phenomenon. An earth day is something hilariously unreliable; it varies all the time. A near earth asteroid would measurably alter it. Today we can measure time with accuracies in the 10^-15 or something, possibly even less. And besides, you're confusing the problem of defining the base unit (second) with choosing its scale and keeping a calendar. The SI second was scaled to look like the standard second used for centuries, just defined more precisely. The problem here is that the "real" second in the historical definition (one nth of a day) varies because of astronomical phenomenons that cannot be predicted (unless you can solve the n body problem for n very large and have inventoried the whole solar system), it's not a time keeping problem.
There's a solution to all this, it's called TAI. There is no reason not to use it but ignorance and incompetence. Every other "solution" that has been advanced here was completely, utterly stupid.
The solution is to keep time with TAI, which is guaranteed to increase by 1s every second, and DISPLAY time in UTC with a TZ on top if you wish. Doing calculations on UTC is bound to result in bugs, people should just forget about it. And also forget about hacking NTP's drift and other mechanisms to accommodate for leap seconds, that's not what they're for. It's just going to add more complexity and reduce precision. It's such an ugly hack I'm shocked that you should seriously advance it.
TAI is simple. It's the number of seconds since a reference date. No days, leap seconds, whatever -- just counting seconds. Want to display local time or UTC? Add the leap seconds and the TZ, and you're set. Want to do a calculation? You can substract TAI values to get nice, friendly seconds without fear of someone pulling the rug from under you.
Get lost, you evangelicals are accomplices in killing thousand times more. Vietnam, Iraq, Afghanistan, and all of South America during the 70s and 80s, all enabled by you US millenarist cultist reichwingers. How you can look down on Muslims while you have so many rapture-enabled evangelicals on your doorstep is beyond me.
In the past two months, every single paperback, and quite a few hardcovers, that I've bought or considered buying have been cheaper on Amazon itself than Amazon's Kindle ebooks. Do printers, ink makers and paper makers charge Amazon negative dollars?
And they want MORE money? WTF is wrong with these people?
Slashdot Mirror
They drove a wedge into Flash. They're forcing web site designer to accommodate people without Flash. That's fucking awesome. Without the iPhone we would have even more sites requiring Flash, and there would be even less competitive incentive for Adobe to improve their terrible plugin.
So yeah, the worldwide Web would suck a lot more if Steve Jobs didn't have that foresight.
And btw, 50% of what makes the iPad great is the battery life. 10h in full use. Imagine if they had flash, people would have no idea why suddenly their battery is draining down. They would blame Apple, because that's what it says on the can.
It's not "mobile" anymore if you need to be next to a power outlet to use it.
Flash on mobile is a joke. On my N900 is drains the battery, you can feel the device getting hot.
Infringement is not decided on the abstract, they all revolve around the claims, which are usually conveniently buried in the middle. What are they?
He cries on TV while drawing absurd diagrams on a blackboard.
If he's not nuts, he plays one on TV pretty convincingly.
He once called a woman on his radio show to harass her by making fun of her for having had a miscarriage. Among other things. He's nuts, he's evil, he's religious. The word for it is spelled c-o-n-s-e-r-v-a-t-i-v-e.
That's the current definition of "concervative" in the US. Most of his viewers probably define themselves this way.
He's completely insane. He fucking cries on TV for nothing. And he's obviously the type of people who would have supported Hitler or any kind of authoritarian leader.
Must be the same.
And since they're quite obviously the type(*) who would want to attend Insane Glenn's meeting ...
(*) morons
Time (and TAI) is independent of time zones. Time zones are a way of displaying time. Just like 10 in base 8 mean 8 in base 10, but represent the same number.
And TAI does not have to be calculated, except in as much as it's transmitted indirectly in NTP (which transports UTC and the difference with TAI), because that's where all official time references are derived from.
not to use binary, because it's very hard for humans to read.
(I was talking about using TAI in a program, not for human communication)
Why are they not? Leap seconds should not be part of the time source, they should be in the display, just like when displaying local time from a UTC clock. Trying to smooth out leap seconds is of the utmost braindeadness.
The most accurate measurement of what though? elapsed time or time of day?
It's trivial to derive time of day from an accurate absolute clock. It's about as hard as displaying a calendar, i.e. not that hard.
On the other hand it's impossible to derive an accurate clock from an inaccurate calendar clock.
The big problem is that leap seconds aren't predictable so it's not possible to convert accurately between TAI and UTC for a time in the future nor is it possible for a system that isn't receiving updates to the conversion table to covert accurately for past/current time.
It's about as difficult as fetching a file over the internet, i.e. trivial. And if you can't fetch that damn file, the only thing you risk is at most a couple second offset when /displaying/. Your calculations are going to be fine; and missing one second on an interval is a big deal (esp. if you're measuring intervals on the order of 1s), while having an offset on a /date/ is hardly ever an issue. And anyway, as soon as you get back to civilization, and assuming you stored your dates in TAI, you can see them accurately in UTC retroactively.
It follows that if a time is repeatedly converted between TAI and UTC by systems in different states of updating (as could easilly happen in a situation where a gradual migration from UTC to TAI is in progress) there could be some rather nasty error buildups. Much the same problem applies with DST but at least most developed countries tend to keep thier DST rules pretty consistent
That doesn't strike me as a very common situation. Calculating time intervals, on the other hand, is a very common task. See time(1).
to affect decay rates. Hint: it generates 15% of the world's electricity.
Clocks should strive to give the most accurate measurement, not lie to their users.
The solution exists, it's TAI. You use TAI internally and convert to UTC (or your TZ) when displaying, similar to unix time.
There's a reason why the second is defined based on an atomic phenomenon. An earth day is something hilariously unreliable; it varies all the time. A near earth asteroid would measurably alter it. Today we can measure time with accuracies in the 10^-15 or something, possibly even less. And besides, you're confusing the problem of defining the base unit (second) with choosing its scale and keeping a calendar. The SI second was scaled to look like the standard second used for centuries, just defined more precisely. The problem here is that the "real" second in the historical definition (one nth of a day) varies because of astronomical phenomenons that cannot be predicted (unless you can solve the n body problem for n very large and have inventoried the whole solar system), it's not a time keeping problem.
There's a solution to all this, it's called TAI. There is no reason not to use it but ignorance and incompetence. Every other "solution" that has been advanced here was completely, utterly stupid.
Accounting for leap seconds is complicated and error prone. It's also completely useless; the solution exists and it's called TAI.
Example: how do you figure how long an operation has taken? With TAI: := tai() := tai() - starttime
starttime
dosomething()
duration
That's it. How do you do that with leap seconds sneaking on you? It's impossible to do, at least reliably.
The solution is to keep time with TAI, which is guaranteed to increase by 1s every second, and DISPLAY time in UTC with a TZ on top if you wish. Doing calculations on UTC is bound to result in bugs, people should just forget about it. And also forget about hacking NTP's drift and other mechanisms to accommodate for leap seconds, that's not what they're for. It's just going to add more complexity and reduce precision. It's such an ugly hack I'm shocked that you should seriously advance it.
TAI is simple. It's the number of seconds since a reference date. No days, leap seconds, whatever -- just counting seconds. Want to display local time or UTC? Add the leap seconds and the TZ, and you're set. Want to do a calculation? You can substract TAI values to get nice, friendly seconds without fear of someone pulling the rug from under you.
Seriously, it's not complicated.
Get lost, you evangelicals are accomplices in killing thousand times more. Vietnam, Iraq, Afghanistan, and all of South America during the 70s and 80s, all enabled by you US millenarist cultist reichwingers. How you can look down on Muslims while you have so many rapture-enabled evangelicals on your doorstep is beyond me.
From my European point of view, they're not any crazier than the evangelicals who supported Bush and who support Zionism.
because "terrorism" is what the Kommandantur was calling the resistance.
you'd be speaking proper English. blimey.
Link
In the past two months, every single paperback, and quite a few hardcovers, that I've bought or considered buying have been cheaper on Amazon itself than Amazon's Kindle ebooks. Do printers, ink makers and paper makers charge Amazon negative dollars?
And they want MORE money? WTF is wrong with these people?
And an analog component within a digital computer does not an analog computer make -- they all have analog components anyway, for fuck's sake.
under my desk. After all, quantum mechanics is used inside it. So it's a quantum computer, right?
Nothing remotely like an analog computer in the TR article, and nothing still on the page you link to.