I’ve voted with Yes, although I don’t use Reactor.
The community approach with the switch to Mercurial opened a whole new world to me. I used to work with svn so hg (with MacHg) really changed my way of working.
I really like the approach, but I have a hard time to get the social approach, I know only to work on my own, I managed to get one issue integrate, but I have yet to discover this proposal board, I did not find it compelling. I do not understand how the Reactor people ‘tick’, where they’re up to, so I’ll wait and see.
I tested Reactor but I finally decided to go the Core route. I am a sole developer with 20 projects online, I depend on a super stable, slowly moving distribution.
Some more personal notes in general :
What I see is that the code get’s more and more complex, (like with most projects) which I really dislike.
CI was once a barebones framework who would shoulder the nasty parts of PHP like email and let the rest up to me. More important, CI was always very straight forward due to it’s simplicity. I loved that. Now It’s getting more and more complex with in parts questionable implementations (packages) or (to me) meaningless functionality (what is a jQuery library supposed to be good for ?). The pure quantity of documentation makes it a lot harder to keep the big view.
I think the core of CI needs a rewrite, a new concept, a restart from zero cleaning up of all the patches since early 1.x (ex: the loading routines), reducing the code, not adding !! A big cleanup, opening the doors for HMVC, REST, sparks and optimization with a modular (cascading ?), easily distributable file structure via hg.
To me the future is in small, lean code, to me the server is the enabler of what I can do on the client side and not a goal in itself.
I want to thank the maintainers of Reactor and the Ellis team, I wish I’d contribute more, for the moment I’am still stuck with restructuring my whole workflow.