Forgot your password?
typodupeerror

+ - BBC Clock Inaccurate - 100 Programmer Days To Fix? -> 2

Submitted by mikejuk
mikejuk (1801200) writes "The BBC home page has just lost its clock because the BBC Trust upheld a complaint that it was inaccurate. All it did was to show the current time on the machine it was being viewed on and not an accurate time as determined by the BBC.
However, the BBC have responded to the accusations of inaccuracy by simply removing the clock as it has been stated that it would take 100 programmer hours to fix. It further says:
"Given the technical complexities of implementing an alternative central clock, and the fact that most users already have a clock on their computer screen, the BBC has taken the decision to remove the clock from the Homepage in an upcoming update."
and
  "impossible to offer a single zonally-accurate clock".
They cannot be serious!
In fact it should be possible with a single line of JavaScript and perhaps a single line of say PHP back on the server. The clock wouldn't be millisecond accurate but in most cases it would be correct to the second.
So a 100 hours or "too simple to fix"?"

Link to Original Source
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

BBC Clock Inaccurate - 100 Programmer Days To Fix?

Comments Filter:
  • Reading some of the comments at Gizmodo ( http://www.gizmodo.co.uk/2013/06/bbc-home-page-clock-to-be-pulled-after-one-complaint/ [gizmodo.co.uk] ) I begin to see the BBC's point. Apart from (possibly) being part of the template code and therefore requiring extensive site-wide testing, it might well probably break their (reportedly extensive) page caching.

    Some there speculate that the old technique uses a client-side function call that is happily cached, while the new version either has to include client-side code that main

    • by crutchy (1949900)

      needs to include a server-generated time specifically customized for that client (= impossible to cache)

      just need an invisible iframe with a js refresh of the iframe and js in the refreshed iframe source that updates the parent time element (sort of web page rpc)... doesn't hurt the caching system

Many people are unenthusiastic about their work.

Working...