Do you guys even bother with frameworks when coding?



Definitely, if the size and complexity of the project is anything more than "simple", I always use Zend Framework, but only for the admin UI. For things where speed matters, , e.g., tracking a million clicks a day through an IM management system, you definitely don't want the overhead of a full MVC framework.

Zend isn't going to make any more difference than gzip output buffering and properly optimized SQL queries... you are mistaken that developing an application (like you described) around a framework is making any difference whatsoever for performance/security/whatever
 
if you are writing single page scripts, framework is overkill.

Personally, codeigniter is suitable to my taste. It's very light (it can even run on your shitty shared poor man hosting), flexible (use whatever your comfortable without bending over), doesn't try to impose itself on you like the rapist Rubyonrails is, which btw is probably the most horrible, bloated, non-scalable piece of shit framework to date. After using PHP, using ruby has it's pluses, but most of the time, you will realize php really has spoiled and made things easy.

One downside of Codeigniter is security. seems like there's a 0-day exploit out ever few months. This is really bad since it makes your site very easy to fuck.

Zend is a piece of shit written by some jew. Don't bother with it.
 
CodeIgniter is fucking amazing. Layered Links is built on it, and I was able to do all of that coding in about 5 weeks because of CodeIgniter. It's MVC based, but not a picky bitch like Rails so you can hack at it a bit if you need to.

Frameworks are a smart decision when coding. They're generally created by coders who are way fucking smarter than me so I prefer to follow in someone else's footsteps rather than pursue some janky coding path I dreamed up.

I have built multiple large systems using CI, things powering dozens of sites and handling hundreds of users, and it is great for rapid development. It's also easy to get started with, so I recommend it to anyone who wants to move forward a bit with PHP.

Glad you are having success with CI.

oh there's also pricks who say Codeigniter is for RAD. Makes me lol. Unless you design enterprise level web applications with Spring, CI is fucking enough.

The nature of CI is really just awesome. You really are free to do what you want, but you can follow their design patterns and secure and clean code.

Rubyonrails is hog full of shit. DO not fall for this clever marketing ploy by 37signals. I spent 2 years working with it until dropping it and reverting to PHP.
 
Me 3. I have sort of a rough framework that I use for this, basically a set of folders called "blank site" (/css, /images, /js and a blank index.html). In CSS I have the 960 framework stuff and a global reset loosely based on the Eric Myers one. In JS I have minified jQuery, which sometimes I end up yanking out. Whenever I make a new site, I just copy this structure and rename the folder to whatever the project is. Saves me some time, but not a ton. Curious to see what you're doing though.

Yeah this is a good approach as well. Framework I would recommend if you need are in invested in the web application for the long haul, and need to sleep easy, and be able to save coding time.

Speaking of Jquery, it's pure win. Look into persistent Javscript solutions out there. It bypasses the need for heavy DB/Server Logic. Which means, infinite horizontal scaling !

There's even some forums and web applications running purely on Javascript + HTML. This makes scaling effortless, since the bottleneck on server side is virtually removed (minimized significantly), and the client browser handles the work !
 
Zend isn't going to make any more difference than gzip output buffering and properly optimized SQL queries... you are mistaken that developing an application (like you described) around a framework is making any difference whatsoever for performance/security/whatever

Sorry if that wasn't clear to you... I was suggesting that in the case of an application where speed is important that you would definitely NOT want to use a framework.
 
I used to use codeigniter, I've built numerous large scale apps with it and it pretty much rocks. I switched to cakephp though a couple of years back, and though not as flexible out of the box, it ,makes up in other areas, and overall, it wins my vote. I also use jQuery, but who doesn't? Its the bollocks.
I guess I'm a bit of a framework bitch, but as previously mentioned, time is money, and frameworks give you an edge if you're working to tight deadlines.