3 ms·
Everything looks like a good idea in a blog post. Your homework, if you are serious about this, is to crack open a non-trivial, but not huge, program and apply
by jerf 12y ago
Everything looks like a good idea in a blog post. Your homework, if you are serious about this, is to crack open a non-trivial, but not huge, program and apply this idea to it. See how the table looks when you're trying to fit a few dozen elements into it in each direction, where the contours of some real problem created the structure (very important!). You can tweak the organization of the program a bit, because changing paradigms often requires tweaks to the best solution, but it's important that whatever the problem was is still solved at the end of the tweaking (i.e., no fair "simplifying" until you've simplified the entire problem away).
I say this not because it will prove impossible or useless, but because you will learn things in the process that will help you refine the idea. Refinement into "what I want is not really possible at scale" is certainly one possible outcome, but there are many other possibilities.
(Certainly one problem you'll encounter is that real code is horrifyingly non-"normal", in the statistical distribution sense. A program of 100 classes is very likely to have 90 of them part of one hierarchy, with the remaining 10 each doing isolated things. Understanding the table representation of such things may have the MEGO ("my eyes glaze over") problem, but then, perhaps you can find something for that.)