On Sun, Jul 3, 2011 at 10:58 AM, rantingrick <rantingr...@gmail.com> wrote: > > Take Pidgin[1] as an example. Pidgin is a universal chat client. It's > a glue between the many chat clients that exist... It's a monkey patch > for chat multiplicity but you get the idea. However the Unity API > cannot be a monkey patch. It must be a mutual undertaking from the > beginning. Don't you people understand? Multiplicity is undermining > our future evolution.
It's protocol glue, not programming code glue. There's a difference; Pidgin replaces "chat client X", rather than piggybacking onto it. Proliferation of code layers results in a performance penalty that proliferation of chat clients doesn't. However, there is still a parallel. Any universal protocol will suffer either from complexity or narrowness - some suffer from both. If every API has to go through this Unity API, then either Unity will be as powerful and complex as C with all its libraries, or it'll overly restrict things. That's why Unity is really just C. ChrisA -- http://mail.python.org/mailman/listinfo/python-list
