Naming in the age of Google

Keyword search works best when a word has a single meaning. Google doesn't work well when something can be contextualized many different ways. A strategy to counter this is to make up a new word (a neologism) when you want to talk about a subject that is otherwise lacking in suitable keywords. I've done it twice so far, and I'm writing this to point to the other blogs where I talk about the subjects in detail. (On the theory that each blog should generally stick to a topic... which I'm starting to believe is a mistake, but I'm willing to wait a while (a few more years) to be certain about it)

A bitgrid is a computing fabric composed of the smallest practical computing element I could envision working when put into a grid. The individual cells consist of little more than a look up table with 4 address lines going in, and 4 data lines going out. The nearest Cartesian neighbors each get an input and output. This makes it possible to do computation on sources from up to 4 inputs having up to 4 output bits.  Most of the time it'll be partitioned differently, though.  It's a continuation of an idea I had back around 1981. The conceptual design space has been pretty much written off since that time by others, as local connectivity only is thought to be far to inefficient use of a chip.

Cabsec is a word coined for me by Doc Searls. It's meant to describe CApability Based SECurity, a concept wherein the user decides that resources from a computer should be given to a program at the time you run it. The nice thing about explicitly supplying the list is that it's almost trivial to enforce from an OS design point of view. It also makes it trivial to stop things like viruses and Trojan horses, because you would have to explicitly allow them to have access to your OS files.


So, a bit of linguistic pollution in the name of launching new memes... a fare trade-off, I think.