Usually the best-liked one is whichever one you've learned. Some prefer Zend for its wealth of features and ability to pick and choose which parts you want to use. Some like Lithium for its support of all the latest PHP features and language constructs.
"Please give us a simple answer, so that we don't have to think, because if we think, we might find answers that don't fit the way we want the world to be."
~ Terry Pratchett in Nation
Depends on the developer, if they want lightweight and near complete control barebones with rapid development, security, scalability.. yes.
If it's basically a clone of most CMS, codeigniter may not be the best decision because it takes longer to develop cookie cutter websites with.
Right tool for the job, most custom applications CI is great. If you're looking at more common CMS - ExpressionEngine is great, which is also built off of CI. It's like a professional level wordpress. Greater speed, security, better quality support. It costs $$ but is worth it.
CakePHP, Joomla and those type of frameworks are a lot more bloated feature packed and in a sense restricted. I find there are more 0day exploits, lesser quality developer community (in average sense.. not saying everyone is bad.. some of the best work with those aswell). You'll find those are used on medium sized websites with lower $$ investments and need for extreme development speed, and no care for hardware required to deploy.
I tend to combine frameworks and cms into 1 for some strange reason when I shouldnt. I consider EE a framework *shrug*
Depends on the developer, if they want lightweight and near complete control barebones with rapid development, security, scalability.. yes.
That sounds like me I like to build sites from scratch because I am so darn fussy and want to design it MY way, but I can give up a little bit of that to a framework if it's going to help me put sites together in a faster and more organized fashion, with less worry of having the shiz hacked out of them. I hope when I'm coding for money I can mostly make sites from start to finish, or it might suck, just a bit. I don't like deciphering walls of code that I didn't write >.>
The better I get at programming, the more I appreciate arrays. Handy dandy things they are.
Hmm, I'm wondering a few things about CodeIginter:
1) If you use Active Record's update() and delete() methods, and forget to use a where() before doing so, will it update/delete your entire table or are there safeguards put in to prevent this?
In the 4 years I did PHP, I was writing MySQL queries by hand, and I never accidentally did this, but it might be in the cards :P It only takes one screw up and there goes a whole table. You can restore to a backup, sure, but you lose what was changed between the backup and the catastrophe.
2) I think I am going to really dig method chaining for database queries. The code you construct looks similar to hand written queries, which is what I'm used to. What is you guy's opinion on doing this? Any drawbacks?
3) Looking through the system files, CodeIgniter appears to use PDO, however, is this just an option or does it use mysqli_* too? I prefer PDO but I'm curious about this.
The better I get at programming, the more I appreciate arrays. Handy dandy things they are.
Most likely PDO is actually using MySQLi (when using a MySQL DB, that is), in that it probably uses the same MySQL API that the MySQLi extension uses.
While I found Active Record interesting and possibly useful, it always ended up feeling like it took me more time/effort to use it than just writing the darned SQL, so I never really got fluent with it and just continued to write the queries myself.
"Please give us a simple answer, so that we don't have to think, because if we think, we might find answers that don't fit the way we want the world to be."
~ Terry Pratchett in Nation
But then wouldn't you have, had to sanitize the external inputs yourself? Wouldn't that take extra time too? From what I understand, Active Record does this automatically (unless you tell it not to.)
The better I get at programming, the more I appreciate arrays. Handy dandy things they are.
Using prepared statements with bound parameters (such as you can do with PDO or MySQLi) take care of the SQL escaping issues.
"Please give us a simple answer, so that we don't have to think, because if we think, we might find answers that don't fit the way we want the world to be."
~ Terry Pratchett in Nation
NogDog: I'm confused. You still had to take the time to prepare the statements before using PDO::execute() right? Does using Active Records takes longer than this?
Mistin: Are you talking to NogDog or me?
The better I get at programming, the more I appreciate arrays. Handy dandy things they are.
CI's activerecord takes care of everything for you, exectute is the equivelant to get() in ar. Each attribute or chain has to be set properly... it's all in the documentation very clearly
I've been trudging through the CI Documentation. So far so good. I haven't seen anything about making queries secure but I guess I'll get to it eventually.
I'm still confused, though, about why NogDog felt like using Active Record wasn't worth the effort. My only experience with them is what I read in the documentation, so I don't know much. I guess I should just wait and see when I start using them? I almost feel ready to try and code something. I just want to read the documentation a bit more.
The better I get at programming, the more I appreciate arrays. Handy dandy things they are.
Once you've written a few hundred (thousand?) queries, it doesn't really take very long to just type out the SQL, just as once you've written a few hundred (thousand?) PHP foreach() loops, you'll be able to write those while watching TV and eating popcorn.
"Please give us a simple answer, so that we don't have to think, because if we think, we might find answers that don't fit the way we want the world to be."
~ Terry Pratchett in Nation
Reply With Quote
Originally Posted by mistin.ca
I like to build sites from scratch because I am so darn fussy and want to design it MY way, but I can give up a little bit of that to a framework if it's going to help me put sites together in a faster and more organized fashion, with less worry of having the shiz hacked out of them. I hope when I'm coding for money I can mostly make sites from start to finish, or it might suck, just a bit. I don't like deciphering walls of code that I didn't write >.>
Bookmarks