Would be nice but my feeling is that the simplicity of SQL CRUD statements could be grokked by way more teenagers in the "past" than will be able to grasp map-reduce in the "future".
Myself I'm also into document DBs and graph DBs, a lot. But for the kind of rapid prototyping that got most of us going as teenagers in the first place, I'd argue table based data with the simplest incarnations of INSERT UPDATE DELETE SELECT WHERE haven't been beaten yet by those no-SQL DBs.
Comments
Would be nice but my feeling is that the simplicity of SQL CRUD statements could be grokked by way more teenagers in the "past" than will be able to grasp map-reduce in the "future".
Myself I'm also into document DBs and graph DBs, a lot. But for the kind of rapid prototyping that got most of us going as teenagers in the first place, I'd argue table based data with the simplest incarnations of INSERT UPDATE DELETE SELECT WHERE haven't been beaten yet by those no-SQL DBs.