Why I switched to Porting to CI

[John Cox]

Hi,

I sent out a tweet the other day that I have been porting X
functionality to CodeIgniter instead of taming X to behave. There
were a couple of reasons:

I needed something fast, and this project was beginning to look to be
a 6 - 12 month port which wasn't in my timeline.

CI offers around 50% of what I need.

It's easier to pull stuff from the X codebase and make it work alone,
then trying to make X work without certain functionality.

A couple of notes. I think X was very innovative in the way it went
about the code. It's just become a beast after 10 years of group
think. Whether or not people will admit it, it certainly shaped
several other "Must Haves" in other projects. That said, it is a
beast now, the UI is a hot mess (just look at the jquery system,
really a mess), and the independence of each sub-system causes a lot
of unneeded overhead.

In my opinion heres a couple of advantages of CI.

It pretty much stays out of the way.

No UI to contend with.

Has (half-baked) core functionality which can be rewritten to not be
in the way of future upgrades.

It has a very small footprint in terms of memory usage.

It ain't perfect though. It has some really weird design decisions
such as not allowing the use of get vars. The code itself is not very
pretty, but since it doesn't get in the way, I haven't really looked
hard at it. The other problem is it is missing some real key
functionality.

I have been porting things as I need them to CI. Next up will be
xarMLString functionality. I don't plan on porting BL over, because I
have gotten used to just:

<?php foreach ($foo as $bar): ?>

<?php endforeach; ?>

everything and moving on.

I apologize for not communicating before this, and just falling off
the map in July, but I had hard project constraints:( I will share
whatever with anyone, and plan to package my X ports up once I finish
with my current project.

Hope everyone is well:)