[eluser]Rick Jolly[/eluser]
[quote author="DChill" date="1291242477"][quote author="Rick Jolly" date="1291162981"]Now a branch is something designed to be merged back into the code base. So I don't see any fundamental architectural changes in the future.
...
The direction doesn't work for me. There are now other, better framework alternatives that share the same philosophy of simplicity.[/quote]
With all due respect, if you find the CI architecture so flawed and feel there are such better alternatives, why are you here? Didn't you choose your PHP framework based on its core architecture, or are you perhaps in a situation where the choice was made for you?
I had the luxury of directing the choice of frameworks at my job, and I chose CI because I felt it was structured in a way that worked better for my team than all the alternatives I considered. Having read a good deal of the CI source code, I'm not here to say it's perfect or couldn't use some fresh ideas, but I'm not about to grab a torch and pitchfork, either.
I think your list of suggestions is terrific, and I hope many of them can be incorporated into future revisions. However, I don't see where they are mutually exclusive with the Community Branch. If you want to develop some new architecture loosely based on CI, I don't see what's to stop you from making the next Kohana, but I'm not at all convinced that turning the Community Branch into a fork is really going to do anybody any particular good. Don't throw the baby out with the bathwater.[/quote]
DChill, you are asking me to give up on CI. I have 4 years invested in it. I must use it for EE development. But most importantly, I don't like to give up.
I don't own a torch or a pitchfork. If I don't get my way, nobody will lose a head.
