As for the unrelated thought, your spot on. I’m hoping that daemon-kit will always be friendly to its users so they never end up fighting the framework. This is a big motivator for the rewrite, the easier it is to “build” the environments, the easier it will be to shape it to your exact requirements. It should be, like Jamis put it some time ago, like “play dough”.

Thanks !

I also think trying things “because they are neat” is actually very healthy. What’s the worse that could happen? You could fail and realize it was a terrible idea that you wasted an insane amount of time on? Right! So what are you worried about? Seriously, I think playing around is good. It keeps the brain from getting all cobwebby.

Random semi-unrelated thought: I saw another daemon library just the other day that would cause me fits. When I build a daemon I often need to build my own CLI interface. I don’t think that’s an unreasonable request. What if I want to be able to queue emails to me mail sender from the CLI, for example. Thus a library/framework that forces me into its own interface limits my ability to use it.

excellent news Maybe the rack analogy is hard to live with, people (me the first) think run time but you mean configuration time… Sorry, can’t think of a better image/comparison to suggest.

Keep up the great work !