Reactor Engineers

[eluser]Michael Wales[/eluser]

@Wales, I don’t seek your approval or that from any other developer. I see limitations in the framework which truly prevent it from moving forward technically as it should. And the Reactor Engineers without the vision to address the issues.

So, fix it - write code and submit pull requests. You are smart enough to figure this out on your own, you don't need us to tell you. Apply to become an engineer - do something other than bitch, which gets us nowhere.

I see the Reactor Engineers asking the “community” what should be in the framework and I find this to be a pointless exercise.

I simply disagree - CI has always been, as you admit, an easy to approach framework. Developers like you, myself, Derek Allard, Dan Horrigan and countless others have honestly outgrown the framework. Sure, we may continue to use it - only because we've managed to roll our own version with numerous extensions or we may be able to "mold" the framework into our vision very quickly - but honestly, you and I both work at a level well beyond the average CI user.

It's the Reactor team's goal to take the work you and I do on a daily basis (both public and private) and gracefully roll that into the framework, document it, and take what you and I know to be improvements and incite the average developer to use within their daily work. Like it or not - we're not average developers, we have over a half century history with this framework - we know shit, have personal preferences, insights and dogma that may/may not fit within the "entry-level" market of CodeIgniter. You and I have responded to literally thousands of posts and I think we can agree - CodeIgniter attracts a significant amount of "noob" traffic, it's ultimately the selling point of CodeIgniter (as you readily admit). The Reactor team can't just leave these people behind for the sake of innovation - it has to be a graceful and slow process.

I really dislike seeing Sturgeon committing every day while the others do very little and really dislike seeing Horrigan’s work committed without open consultation about its value.

To a certain extent, I agree - Phil is working his ass off and bless him for it. Do I think Dan's work is being committed without being pitted against the coding/documentation standards of the rest of the team - absolutely not. Lest we not forget, Dan was an EllisLab employee - he's used to working with these requirements in place. With that said, could I name a single other developer on the Reactor team? Nope. I partially contribute this to the fact I have been absent from the community for a long time but overall, I think the Reactor team needs to do a much better job in regards to transparency. Overall, I think it's a downfall on EllisLab's part - they created this beast, they now need to support it. Recently there was a change made allowing models to load subsequent models (sorry, the developer's name escape me - case in point). Fortunately, the developer made an excellent blog post in regards to it, detailing everything you would need to know - this should have been mirrored by EllisLab on the CI blog.