Very interesting. I like how this seems to let application logic live as close to the UI as makes sense. That is, there's no barrier, intermediary or anything

Very interesting. I like how this seems to let application logic live as close to the UI as makes sense. That is, there's no barrier, intermediary or anything else that might drive them apart. Of course, applications have a higher-level structure that isn't just an artifact of the framework, and I'm curious how this system would work out in real life once you start grouping/composing cells and having them communicate to implement that structure. Each cell has a pretty uniform "surface" -- that is, the properties it has and what they mean, so it should be possible to "snap" them together easily and in any configuration. I wonder if it's too flexible, in a sense, meaning you would need to be careful to use higher-level patterns to organize your cells so that your app doesn't become a messy blob of cells. These are just thoughts after a static reading of it. I'd like to play with it and see if I can get a better feel for it. One thing I don't like is expressing HTML in JavaScript objects. Seems like we ought to express HTML in HTML! I wonder if "cellHtml" might be a better approach to this than cellJs -- that is, where a cell is expressed in HTML (would still have init and update JavaScript functions, though) I don't know if that's workable, though.