Probably all those cheeky sales strategies like auto-renewal at any price without confirmation. A free email box that turns into a paid one and can only be cancelled with a support ticket. Shit like that certainly annoys me.
I think you interpreted "the whole issue" differently than me. I know from years of experience that PC clocks are notoriously inaccurate - it's nothing to do with timezone, they are just very cheap timepieces.
I interpreted that in probably more than 95% of cases, people clocks were wrong and they were annoyed that the BBCs clock was the no improvement - Their machines are probably not using NTP, otherwise they would be fine.
This is the interpretation in the article as well.
You should be able to get the local user's timezone either from their environment, or if using PHP, there is a function call for it as described in the article.
Everyone knows IP lookup is a guess at best. Google DNS uses this plus latency checking to improve location estimates.
I think you maybe focussed on reinventing the wheel to much. It's really not that hard to have a clock that is more accurate than the local machine presented dynamically on a webpage using your local timezone. Off the top of my head, I was trying to think if JS could get NTP or such directly, but if using PHP, one could rely on the servers clock passed to the client to make an adjustment as described in the article - the server of course, uses NTP.
The BBC doesn't need to set up their own NTP server with their own clock, there are a heap of accurate time sources available freely. If they pass their own servers clock, there would be no extra load on external time sources.
"Um, WTF? Did you even read what you wrote?"
Snarky little Slashdotter.... STFU.
"It turns out it is actually difficult to get time zones right,"
Ok - I am assuming that to use the clients environment for Timezone is sufficient, you are assuming it isn't - that's fine, so you'd need to do a best guess based on IP lookup google DNS style from the server - combination of IP DB and latency checking.
I know most clients clocks are not precise, but if they have their timezone wrong, I don't why that's the BBCs fault.
" It needs to be taken every time situation in the globe"
Even after fixing your English, this is completely false for global GMT, local timezone.
You just joined the heard of idiots because you don't know what you're talking about... I have already stated that I don't need to take my own advice on this one and why.... so STFU typical Slashdotter.
I get tired of the "experts" here coming up with what they think is the obvious solution - different to everyone else's and mostly just made up BS.
People calling each other out on such utter nonsense.
Please Slashdot, if you don't know what the fuck you're talking about, STFU!
How fucking hard is it really to have accurate time displayed on a webpage ?
I haven't tried it myself, I don't claim to have the ultimate solution, but it does appear to be a no-brainer.
Firstly, I'd be looking for a stdtime server that can give me GMT in some kind of XML or JSON - this would make life easy. if not, then maybe see if NTP can be interpreted by JS.
Then I would establish how hard it is to read off the local timezone from the clients environment, then it seems as though you just combine the 2 - the correct global time and your correct local timezone - these are the requirements, nothing more.
As you can see, I'm not talking out of my arse, just pointing out that it would take a morning to investigate the feasibility of the above and fulfil these requirements - most likely the extra code would be a few days at the most.
I think that is the point - the BBC haven't even done any basic research into this.... they just mouth off some BS as if they were on Slashdot themselves bagging everyone else's solution.
2. An average craftsmen working with bad tools becomes a bad craftsmen when he is afraid to admit the tools are bad.
3. A good craftsmen blames his tools when they are bad and himself when they are not - otherwise he does good work with good tools for that is why he is a good craftsmen.
From experience, I'd say most people who state no. 1. as paramount are actually number 2. The number 3. people don't usually talk about it too much and they usually think they are number 2. Personally, I think C++ can be replaced by Go and nothing can replace C.
The math is ok, but it fails to take into account that raw pixels are not we see at this level anyway - this class of pentile display produces the full resolution for luminence and a lower resolution for chroma - our eyes don't perceive the pixels, our brains process luminance and colour from different sensors and produce an image from that information anyway.
I don't know about you, but when a display is just blue, the precision is lost on my eyes - I can't see the same precision as I do with white at all - was the same for older LCDs and now on my galaxy S3.