> Now what do you think about Yaws maintaining a simple key-value store
> for users? Could it be part of the "infrastructure" or is it outside
> the scope and ought to be provided as an addon?

Honestly, I think it should reside outside yaws since itīs so incredibly
easy to implent outside yaws.

Yes, it is (for me I would say fairly) easy as many things in Erlang :-), so I won't argue about this. The case against everyone rolling their own stuff is that you do not build infrastructure and maintain isolation between applications, while a common store/registry could provide a foundation for applications to interwork, publish interfaces or whatever - and so you may get "synergetic effects".