Form factors are so important. I'm right in between robots and toasters. I see a building as the form factor for a 100 year computer.

The best illustration of this subtle difference is how I'm contemplating snow and ice management. I have the solid state idea of installing quartz IR lights around the building to control the ice and snow. I also have been working on using de-icing and pre-icing liquids with hopes of getting some droids to take over the physical part of applying the liquids and brushing away the snow.

I have settled on doing both with the building controller acting as the overall manager of the process.

I looked at the posetree.py that the author wrote and linked to and it looks like as good a place for me to start.

Form factor is critical in assigning human names and commumnicating use. I find when organizing a solution to a problem adopting a form factor too early is a hidderence.

It's a matter of interface: people like the idea of humanoid robots because all the interfaces are already optimized for humans, thus if robots have that form factor they can use the same devices/tools that humans do and we wouldn't have to change the designs of these machines.

The question is: how much information is lost in the process? How many layers of complexity we would add to a machine ensemble to be able to operate together at a satisfactory level? The machine learning corollary of understanding the whole picture of the problem/solution space and that leading to simpler solutions (because you don't have to optimize further) applies here. At the end of the day, cost, complexity and practicality will have the final word.

A toaster cannot make a toast alone. It has to be inserted and removed and put on a plate. That's what I want a robot for (one day, after I am sure, it will not accidently toast me).