Timeline of a Car Crash
drive.com.au
drive.com.au
http://www.drive.com.au/Editorial/ArticleDetail.aspx?Article...
It's easy enough to click "refresh" on a web server running on your desktop and wait half a second for a refresh...but then when you ponder that not only might you be executing a few THOUSAND or TENS OF THOUSANDS of lines of your own code, but you're executing a few hundred SQL queries, each of which is doing mind-bendingly complex stuff over in the SQL server ... running the same CPU ... it just boggles the mind.
I remember when I was amazed at how many computations my overclocked Apple IIe (running at 2.5 MHz !!!) could do in an eyeblink.
(edit: light travels about a foot in a nanosecond, or 6 inches per clock cycle in a standard 2ghz pc. multiple simple additions can be done in a single clock cycle; multiple by number of cores)
That said, it's been at least a process generation since a given clock signal could be used to synch events on the opposite sides of a core, let alone a (high performance) chip. This is due to both increasing clock frequency and the fact that propagation speed has gone down as feature size decreased.
A false-negative could exacerbate the injuries of the passengers. A false-positive could cause a fatal crash. No room for error.
Amazing stuff.
Worth a read, and very apropos.
I enjoyed that a lot, thanks.
Amazing.
B) I think they're just making the point that all this occurs before the brain can register what's going on to begin with.