1 to 8 of 8
Mainly for people who use CI, as I know there are few on here, (or people who did, at any rate). Are you guys all still using it, and if so, are you not getting more and more worried about the lack of updates and the general 'falling behind' of the framework compared to others?
I'm still using it for stuff, but am really missing vital features that I don't trust palming off to non-core developers, or people who haven't been vetted as able to commit to the core framework. Stuff like proper PHPUnit integration, better models, (ORM and non singletons would be nice), migrations etc.
Do people still use it for new projects, or are you moving to new stuff? I always look around but in the PHP world nothing has as much documentation and community as CI, but lots have better features...?
Thoughts?
Have you been reading some of the stuff that was written over the past week? To summarize, Ellislab basically said that CI is something they see as a 'gift' to the community, and they used a lot of language that implied a large amount of ownership over the framework. There were also lots of responses from other developers complaining about lack of access to commit to the core and the stagnation of the project over the last 18 months - which in my eyes is true, it is missing so much more than Rails 3 now.
I'm considering looking elsehwere, (and I thought of Rails too since I am using Ruby a bit for scripting now), but like you, have a lot invested in CI.
http://news.ycombinator.com/item?id=1851161 contains the relevant info ...
It's a big worry really, one of the hardest thing is the sheer amount of alternatives out there. There's 80 odd just for PHP alone.
Pretty much what Gecko said. The only other framework of interest to me is Rails but it's going to take something big for me to switch there.
Yeah, I saw a lot of hoo-haa about it last week. I've put it down to precious open-standards worshipping developers/bloggers with mouths bigger than their brains getting on their high horses about morals, the notion of ownership and a load of old bollocks that has no place whatsoever in business.
As I understand it, CI 2.0 is pretty much ready (we're actually using it on a production project), and I totally understand EllisLab's position on it. It's not like they're going to stop developing it, and if you look at the commit history it's actively being worked on all the time.
The development 'community' really get on my tits sometimes, I'd be fucking furious if I were EllisLab, kudos to them for being calm and professional about it.
PHP4 support has been dropped, so it's on the way to being all PHP5 (speed/efficiency improvements behind closed doors as well as the ability to create functionality that couldn't be made PHP4 compatible), the ability to create application 'packages', so if you want to use a third party 'module', it's no longer a case of dropping a library into your library folder, a view into your views folder, etc -- they can all be packaged up into a single package folder. This has some serious advantages.
Also, you can create 'drivers', which are a clever way of extending classes (eg: you could have a Javascript class with a JQuery 'driver') without getting all clunky.
Ability to extend core libraries.
More flexibility in the db config.
This is a good summary, if old: http://philsturgeon.co.uk/news/2010/03/codeigniter-2
Overall it's just neater, tidier, cleverer and more extensible. It's far better than 1.7.2.
1 to 8 of 8