He's referring to generating 1.21 jigawatts all the way back in 1955, which wasn't a time when plutonium was available in every corner drugstore.

The AT&T merger with T-Mobile was effectively blocked. In that case AT&T withdrew, but it was clear to them it was going to be a tough fight with the FCC. It ended up costing AT&T a $4 billion fee that they paid to T-Mobile.

What the hell is a Jigawatt?

Anybody Want a Peanut?

Those are the shrieking eels!

Donâ(TM)t call me Shirley

Total Recall?

⦠into an account that we open.

"What the hell is a jigowatt?"

The only winning move is not to play

I complete agree as well. Are there particular fads that you find to be bad. I think the "problems" most of the newer frameworks are made to solve were already solved a long time ago by smarter people in ways that made a lot more sense, were less complex, more flexible, and performed better. I can't stand this "newer is better" attitude about frameworks. These younger developers think us older folks are stuck in our ways, but why should we use new frameworks which are terrible?

Imagine trying to explain to todayâ(TM)s youngsters how it had a spinning disk in something you held in your hand.

It was such a dumb motto to begin with

Interesting, why donâ(TM)t they do negative caching anymore?

I bet this is something someone in their 40s or 50s would have pointed out as a risk, only be be laughed at by a 25 year old Facebook employee saying that such a failure scenario would never happen.