The problem in my mind remains that many of the j-c projects are very Java focussed, or solve problems specific to the Java language. Even if you wanted to write a similar kind of component in another language, different design decisions would be made based on what is available already in that language.
I think there would/should be some collaboration between, say, a C-based HTTP client and a Java-based HTTP client. The problem they are attempting to solve is the same. They can pool their resources and come up with common strategies to dealing with 'real world' issues. How should you handle chunking errors? The design patterns in the code may or may not be similar though. But, what if they collaborated and came up with a similar API? Wouldn't that be exceptionally powerful? I think so.
And, I think *most* 'non-Java' people can grok Java (at least read it). I just wouldn't choose to write anything in Java unless I was forced to. But, that's my own personal bias and says a lot about the types of applications I usually write. -- justin
