Ever hear the advice, "Beware the old man in a young man's game"? Every couple of years a new upstart claims some fundamental flaw and illustrates how they wou

Ever hear the advice, "Beware the old man in a young man's game"? Every couple of years a new upstart claims some fundamental flaw and illustrates how they would fix it. The industry has a lot of upheaval with new leaders emerging from the pack constantly. But after almost fifty years, SQL is still there. Folks have ORM'd it countless times. Tried to apply it to their popular (and unpopular) language. Implemented new database styles with novel access methods. And SQL is still just as strong if not stronger than ever. So either everyone just goes along with the old man out of habit despite the prospect of tremendous personal gain and advancement… …or there's something important (or many things) the young upstarts just aren't recognizing about that old man—to their peril.