You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
And also remarkably close to the irritating fact that clock speeds seem to have just barely moved over the past 10 years.
There's a lot of what-aboutism in the replies. Saying "but what about parallel computing / pipelining / GPUs / ASICs" etc isn't a response. Ideally, we want faster clock speeds _and_ all those things. Clock speed stagnation isn't something to brush off.
We had a huge effort on this at DARPA. A key consideration is clock skew across the device as speeds increase. You end up with "clock domains" that shrink, large overhead in mitigating skew, and what effectively becomes a multicore architecture for fixed die size
Interesting! What causes the skew / how do you resync or mitigate it?
Is there a hard bound on clock speed other than Planck’s time?
It's not even entirely clear that the Planck time is a hard bound, though I guess a lot of physicists would say so.
The wavelength of 2.5 GHz is 12 cm. At some point, you gotta accept a hard physical cap on frequency.
“The Free Lunch is Over” discussed this in 2004, and with the benefit of *15 years* of hindsight, it is amazing how absolutely correct it turned out to be. One of the most important essays I’ve read in my whole career. http://www.gotw.ca/publications/concurrency-ddj.htm …
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
