Normal people use spreadsheets. These spreadsheets then grow into monsters.
What's needed is an invisible migration path so that people use what they understand but have somewhere to grow when they start abusing formulae to do what a real RDMS would do naturally.
It's essentially a UX problem - to all extents and purposes a database == a spreadsheet with multiple sheets - as soon as you start defining relationships between the sheets.
Joel Spolsky also has a great essay about this: http://www.joelonsoftware.com/items/2012/01/06.html
"What was I talking about? Oh yeah... most people just used Excel to make lists. Suddenly we understood why Lotus Improv, which was this fancy futuristic spreadsheet that was going to make Excel obsolete, had failed completely: because it was great at calculations, but terrible at creating tables, and everyone was using Excel for tables, not calculations."
Excel is used for a great many things, lists, calculations, analysis, charts, storage, and all of the possible mixtures of the two.
That said, airtable does look pretty cool. As someone terminally addicted to Excel, and looking at Microsoft's recent responsiveness to market dynamics, it makes me wonder whether if this was a major market opportunity, they could create a special "realtional DB tab" in excel and capture 90% of the functionality. Interesting to watch.
Agreed with you on the next gen of spreadsheets, being more powerful spreadsheets. The OP is playing their book: sure, Airtable can do list-taking - and I use Evernote for that - but it sure ain't going to replace Excel.
Really, I think it misses the point. Databases are about storing data, and admit a wide array of front ends, and there are plenty of tools now to use spreadsheets as a front-end for databases (most spreadsheets have basic tools for this built in, and more advanced ones are available.)
Spreadsheets are about viewing/manipulating data, and can both natively store data (in what is, necessarily, a database, though perhaps not a relational one) or connect to foreign sources for it.
"The next generation of spreadsheets will be a database" is a silly statement, for that reason: its possible the next generation of spreadsheets may have a particular kind of database (say, relational) as a native, internal storage system and expose tools for working with it. Or the next popular database front end -- the next Access -- may be a general purpose spreadsheet with the right tools.
And maybe spreadsheets, as a viewing and interaction tool, will be replaced with something with a different more mobile/touch-friendly UI paradigm, as the article seems to suggest (but doesn't really present much of a case for -- making vague suggestions about how spreadsheets don't work on touch [that remind me of the kind of hyperbolic descriptions of why current solutions don't work typical of infomercials] without any suggestion of what concrete elements would work better is not making that case.)