* How does Objective-Cloud handle circular references (will memory leaks be a problem?)
* Is there a way to cut down on boilerplate (having to declare member variables, accessors, synthesize them, and understand the differences between var = _var, self.var, static class vars, etc?)
* Any plans to port to other platforms (Android) and if so, will it still use objective-c?
* How do you sandbox binary code (will security be a problem?)
* Will you allow third party binaries/libraries to be uploaded with the code (or will everything be open source/code only?)
To be fair, I believe that this style of development may be the future. Perhaps we need a wrapper around pure C because it doesn't do enough to promote inter-module communication, and C++ dropped the ball on that.
I'm just concerned because objective-c is ideologically different from, say, Boost, D, or Go. It focusses more on patterns than abstractions and simplicity over correctness. I've found it nearly impossible to build an app in obj-c above a certain size that's guaranteed to run indefinitely, stably and without leaks. And I've found that large obj-c projects often lead to spaghetti code and repetition, because of a lack of understanding about things like delegates, inheritance, using notifications instead of nesting code, etc. Some aspects of obj-c are quite brilliant (like queuing tasks on the main run loop) but others like manual memory management are antiquated.
But kudos for this effort. I'm curious how this plays out.