I’ve long been a proponent for rewriting rather than slowly iteratively fixing, once you’re at a certain level of technical debt. The success of this project really strengthens this idea for me, and I’m really really happy with the result!
Also, writing stuff in C in this day and age feels pretty great.
We're working on a version of the library that is AppStore-safe, e g for the bug reporting use case. It's not nearly as performant, but works good enough, at least in iOS 7.
Yes. I haven't optimized it for games yet (there are several shortcuts you can take in such a scenario), but it works fine for the OpenGL games I've tried with.
Hey, also cofounder here. It should work fine, but you'll have to write a little bit of Objective-C for it. We plan to make it a drop-in kind of thing for PhoneGap, RubyMotion and other such tools.
Except those can't read nor modify variables in their enclosing scope. Anonymous inner instances are more akin to C's nested functions, which GCC has had for a long time.
Correct me if I'm wrong though (which would only make me very happy); been years since I did Java.
>Or rather, a large organization could only avoid slowing down if they avoided tree structure.
Valve, the makers of Half-Life and Portal, work like that. No one has a dedicated role, there is no hierarchy, there's just a guy with a vision and a large team of widely-talented people who work on what they want to work on. Obviously it works, too :)
Also, writing stuff in C in this day and age feels pretty great.