[kats]

Some random thoughts, might be interesting (or not).

Some things that really do fit into tables, where there's no empty fields in the rows:

- Relational databases

- Hardware circuit truth tables

- Assembly language opcodes

- FPGA compiler output

- Matrix multiplication. Or some GPU programs e.g. if you want to have a conditional statement using multiply-add, then 'if (cond) then x1 else x2' would be 'out = (cond * x1) + (cond * x2)'.

Those things have good performance in one way or another. But it's not easy to make all the application logic fit into a table-based schema.

e.g. Why does someone choose a python web server framework which sends and receives JSON. It's really super easy to extend and add something without knowing what you'll need in advance.

But if you try to fit that into a table, you'll have to change the table schema for everything to try to best fit what the program does right at the moment. And then if there's one new extra complex or long-running function, it will never easily fit the same schema as the others. You'll have to break the big function down into some smaller common operations.