Chrome doesn’t attempt to sandbox CPU consumption. I just closed an inactive Google docs spreadsheet, and saw CPU fall from pegged-at-100% to bubbling along at 10%.
Does it really need each available CPU cycle to wait for the other end to do something? Apparently so, in the way it’s coded.
Google: not as clever as the press release makes out.
Let's say, for example, that a system supplies you the time of some event in UTC, you convert it to local and shove the date/time up on the display. Say, for argument's sake, you also include the Day Of Week, ending up with a format of DD/MM, DOW HH:MM. Everything looks fine, until someone notices that the Day Of Week is wrong. The 28th of May is a Wednesday, not a Thursday.
The date conversion routine that generates the DOW string does a bunch of odd stuff, bu
t seems to work correctly; it certainly works in other parts of the code, and generates the right string there.
The UTC time seemed to be converted to local time twice, but that wasn't the culprit; surprisingly, no-one is killed in an explosion of silicon splinters when that code is double-executed. Whatever.
Could it be that the system supplying you the time of that event in UTC is off by a year? One year into the future. That would give you that behaviour.
Here’s the algorithm for checksumming a credit card number, plus information on what all the fields are.
But you can checksum the numbers all you like, if the signature doesn’t match the transaction never happened.
Here’s an idea: rather than sending advertisements to user’s computers, why not send scripting code to calculate [the valuable thing, like, I dunno, pi or hacking the encryption on HDDVD or something] and send the results back to your central computer?
Come on, you know you want to. And it’s free!
Two new AJAX have been released recently.
Yahoo AJAX Patterns has code and a set of patterns published under a BSD/Creative Commons license.
IBM’s AJAX Toolkit Framework is IBMs version.
Of course, Microsoft have their own version, called Atlas that’s built into ASP.NET 2.0.