4 ms·
If a DB is truly a store of data, then any language interpretation is going to be done by a language interpreter/compiler and not by the functions that store an
by dtagames 3y ago
If a DB is truly a store of data, then any language interpretation is going to be done by a language interpreter/compiler and not by the functions that store and retrieve data. You could think of SQL as a language that operates "inside" a database (though I would prefer the term "against" a database). With any Lisp, like Wolfram, you are halfway there as the language mixes data and instructions on purpose.
- dennisy 3y agoAhh ok, so you are saying Lisp is more specialised in this direction vs say Python to Java? Sorry for the ignorance but I have never used Lisp.
- dtagames 3y agoYes. In Lisp there is no difference between how code is stored and how data are stored. Both are available to the REPL (a command line interface) which does allow for a different style of "live" development. Although Lisp is powerful and fun, it's of note that the inventor of Lisp quickly turned his back on the concept to invent Algol -- which is the basis of nearly all other modern languages that aren't Lisps. In practice, mixing code and data often turns out to make things worse.