Re:Predictions on the future of databases
by dangoldin on Monday December 16, 2013 @06:17AM
(#6914051)
Interesting - thanks for sharing that. It highlights the disconnect between the theoretically correct solution and the practical one.
The object-relational mismatch is still a huge problem. I'm quite interested by this supposed solution. But I spent 5 minutes chasing links and couldn't find an example of what the syntax actually looks like, only a suggestion that I buy some book to understand the language. This "D" thing sounds pretty cool, but it seriously needs some more user-friendly marketing (and a non-colliding, googleable name).
Re:Predictions on the future of databases
by siddboots on Monday December 16, 2013 @04:26PM
(#6917925)
Tutorial D is an example language spec, but the syntax itself isn't really the point.
D would overcome the object-relational mismatch by making the relational side much, much more powerful. It's really about unifying the ideas of "tables of data are relations" and "relations are logical propositions", so that one could have an über-powerful general purpose language that just happens to also be a natural interface for databases.
D is essentially a set of low level prescriptions that the authors felt would be required in order to achieve such a language.
Re:Predictions on the future of databases
by dragonwriter on Monday December 16, 2013 @09:36AM
(#6914911)
Most of theninterestin info is linked from the reference material section of www.thethirdmanifesto.com; what you Semmelweis to be looking for is:
http://www.dcs.warwick.ac.uk/~hugh/TTM/Tutorial%20D-2013-05-...
Which provides a description of Tutorial D, an implementation of the prescriptions.
Re:Predictions on the future of databases
by dragonwriter on Monday December 16, 2013 @12:16PM
(#6916154)
> ... Semmelweis ...
Or "seem" -- I have really no idea how that happened and didn't notice it until too late to edit.
https://en.wikipedia.org/wiki/The_Third_Manifesto
The difficult problems since that time turned out to be scalability and parallelism, neither of which were addressed by The Third Manifesto. So instead of D, we got Map Reduce and NoSQL.
Who knows what the hard problems of the next 15 years will be.