I don't think that zk is hard to get right.
What is hard is to layer a very different model on top of ZK that changes
the semantics significantly and that that translation right.
One of the very cool things about ZK is how easy it is to write correct
code. I know that Ben and co put a lot of thought into making sure that the
API would encourage correct behavior.
I am very sorry if my words suggest anything different.
On Tue, May 4, 2010 at 2:58 PM, Adam Rosien <a...@rosien.net> wrote:
> I'm a bit frustrated that zk is "very, very hard to really get right".
> At a project level, can't we create structures to avoid most of these
> errors? Can there be a "standard model" with detailed assumptions and
> implementations of all the recipes? How can we start this? Is there
> something that makes this too hard?