Every time a framework pulls a big set of data across the wire to do a local calculation on it (a for loop summing a list of values, for example), it's doing a completely unnecessary round trip to do (probably in PHP or Ruby, no less) a task for which the database has already been specifically optimized. It could have done all the calculation during the same pass it took to select the records and just sent the answer instead.
Frameworks obscure this.
Just a thought.
This is not what relational databases were designed for.
Otherwise your comment is correct.
Interesting data point, by the way. I have a little USB flash drive that stores 4 GB. It was about $10. That's probably more disk storage than existed in the entire world until Y years ago -- any idea what year?
I have to respectfully disagree. Its often when a tool becomes so ubiquitious and sufficiently intuitive that its true power comes to the fore.
It is like the electric grid, when it was first being forged everyone who used it thought about it extensively, now hardly anyone does. But that does not mean the grid's prime time is over, it means that now it is truly becoming powerful.
The prime time for SQL has long been over, it is a necessary tool most of us don't think too much about.