So lets talk the inner join

My claim is that the inner join, and all other software atomics, can be viewed as a mutual traversal by two graphs, so my generalized lambda operator fr Lazy J becomes the @, You don;t always have to type it, often your environment knows it.

as in:
MyResults@{ {word1,word2,word3},SomeTableOfWords}

Get you a Qson full of results, ship it right back. But lets talk the wild cards. First null:

@words,_

Run something called words along the null graph. Probably the null behavior his is to echo whatever words is. What is the default way for the machine to figure out words?  The machine, being what it is, would think words are a table, by default, and if not, then some immediate string constant. So, in the default, just type the table name, and it regurgitates.  How about this:

@config,SystemInstall

One would expect the machine to look up config as a table, and would certainly know what SystemInstall is, right? I dunno, tying for the very simple, as usual. But the idea here is that under the @ operator, natural symbols for the machine come into play, it has a more liberal use of symbols.

Hey, what about dropping syntax uglies like I do? Why not, or why not connect up better shell, one that emits Json into the machine?