(08-03-2016, 09:50 AM)cartalot Wrote: One of the hallmarks of Codeigniter has been that its not dependent on any third party code. What happens when there is bug in the third party code? Its a big problem because unless the developer fixes it immediately the community will be forced to create a fork. Codeigniter is a great platform because its very stable. Releases of Codeigniter are in production for years. The reality is that most third party libraries are abandoned, OR they put their energy into the next version - with a bunch of breaking changes that will no longer be compatible with Codeigniter 4.
That's probably the best argument I could see. Though I would say the hallmark wasn't that it didn't depend on third-party code, but that you had a single download and you're good. We'll still have that either way.
To be honest, we've already using two third-party packages. And it's definitely not something we do lightly. The first is Kint, an awesome debugging tool - that only applies in the dev environment and if there's a bug, then it's not that critical if we can't get it fixed. The other is Zend Escaper because it's written by some of the most knowledgeable people in the business when it comes to safely escaping output. And it's backed by Zend which will be around a while, I think.
There's always a fine-line between keeping it in-house, and the potential insanity of rebuilding the wheel just to say we did.
Looks like the "No" group is winning, so we don't have to worry about it this time around. Just when reading through all of them the other day it was sounding like a more OO-approach might be in order, which would mean do it like everything else and use an interface so people could extend, which made it sound like a potential rewrite of FlySystem. Hence the post.
