Slashdot Mirror

I found something like this to be helpful instead a cms https://codeigniter.com/ and if google wants to remove things from their search results try removing generic brandings like "powered by wordpress" ect...

Most hate towards PHP comes from elitist snobs who don't know how to use the language. PHP is perfectly fine language to use, and it is extremely powerful and flexible. If you are going to develop for web, I suggest using some framework, as it makes the process much more straightforward, faster and better. I personally use CodeIgniter, which is fast and has a good library of helpers and other essential framework stuff. CakePHP is often suggested for persons new to frameworks, but I would stay away from it. It's slower and it's more pain in the ass to learn.

That's right. Most people who hate PHP don't know enough of it. That's why I hate it. I could never learn how a well built application should look like in PHP.
That's why _I_ wouldn't buy anything made in PHP, it's too hard to tell good from bad, for non experts.
If you are an expert in PHP , it's OK to use it, I wouldn't pay you to do it, because it's too hard to tell if you are really an expert, and it's too hard to get another expert if you change projects.

Most hate towards PHP comes from elitist snobs who don't know how to use the language. PHP is perfectly fine language to use, and it is extremely powerful and flexible. If you are going to develop for web, I suggest using some framework, as it makes the process much more straightforward, faster and better. I personally use CodeIgniter, which is fast and has a good library of helpers and other essential framework stuff. CakePHP is often suggested for persons new to frameworks, but I would stay away from it. It's slower and it's more pain in the ass to learn.

There's also other good things about PHP. First of all, it works with practically every web host out there, and doesn't require you to play around with it to get it work. It has an extremely comprehensive library, amazing documentation and almost all API's have client libraries for it, if they just have some. PHP, being the #1 platform on the web, gives you that advantage.

Two of the best open source projects that I first learned about and utilized for "real work" in 2008 (though I don't know that they count as "victories"):

Puppet, the system administration automation system. (Like cfengine, but way smarter and easier)

CodeIgniter, the PHP web application framework that doesn't box you into its idea of a web framework

Rails definitely uses more CPU time. However, it can make development of some kinds of things much faster, and you can work at higher levels of abstraction in Ruby than PHP.

Wow, color me surprised, a framework for a language makes development faster than the raw language. It's a shame there aren't frameworks available for PHP that could cut development time in a similar manner as Rails does for Ruby...

CakePHP Framework (supports PHP5 & PHP4), Version 1.2 Stable due any time soon.
Symfony. PHP 5 Meta Framework using Propel and other layer components. The accompaning book (free PDF, buyable dead-tree) is a very good documentation.
Prado. Event-Oriented PHP 5 Framework. Very interesting.
Code Igniter. Lightweight PHP Framework for smaller stuff. Neat website.

Django. Python Framework.
TurboGears. Python Meta Framework using some 3rd Party stuff like Templating layers and such.
Zope Web Application Server. To date unmatched. What Rails wants to be when it grows up.

If you use PHP4 you can use CakePHP or CodeIgniter If you use PHP5 you can use Symfony, CakePHP, CodeIgniter or the Zend Framework. CodeIgniter has good documentation and its 100% complete unlike CakePHP. http://codeigniter.com/ Of course PHP has many more frameworks than the ones I mentioned, there are probably well over 15, but those are the ones with the biggest amount of users. From what I've read the Zend Framework is more like a big library and lets you pick and choose what you want with no set structure. I've seen tutorials where others can use the Zend Framework with CakePHP, Symfony and CodeIgniter. The pros to sticking with PHP or a PHP framework is that you probably already know the language. Need security tips for PHP? Visit Chris Shiftlett's blog (he does a good job covering several issues, plus there are books on Apache Security and PHP Security, get them and read them). http://shiflett.org/ I dont see PHP dying anytime soon, there are way too many open source apps written in it, plus tons of new stuff is coming out, like SimplePie, and other good stuff. PHP Developer's web site has some good news on it. http://www.phpdeveloper.org/ Django and Rails have a downside to you having to learn a language and a framework and most often at the same time which makes things confusing for awhile. Django isn't 1.0 yet so while its stable, its still undergoing changes and nothing is exactly set in stone until the 1.0 milestone. Unfortunately there arent any Python books for just Web Development, so that makes it more of a challenge. Rails has a definate lead over Django, since there are well over 100 books on Rails and only like 2 planned for Django. Of course Rails was got more hype earlier on and came out before Django, plus the screencasts helped promote it, a lot. Pick whichever language or framework you want, there are pros and cons to them all.

>CakePHP is a typical PHP open source project: random code, bloated, no direction. It's also cool, in a way, but I'd never run big project on it.

Why don't you check out CodeIgniter, it's neat, imho.

Your way of thinking is outdated. There are many frameworks that facilitate proper MVC, templating, and a separation of duties. Check out CodeIgniter, CakePHP, and symfony, three of the most popular frameworks for PHP. Development techniques and approaches in PHP have changed significantly in the last few years.

You will want to use an MVC (Model-View-Controller) paradigm. The Model contains your data work (accessing database, data manipulation, etc.). The Controller directs the application what to do, and the View is the final result (HTML).

The View can contain minimal PHP that's only used for display purposes. No data manipulation is done here (other than walking through records, for example). Alternatively you can use templates, but the point is moot because you're adding a layer of abstraction on top of what PHP already does -- templating.

I recommend CodeIgniter as a simple framework for any future applications you build. It's based around MVC, has a small footprint, and is very easy to learn and work with.

I'll second that. CodeIgniter http://codeigniter.com/ is less than 6 months old, but done by the ExpressionEngine folks, and is a really good PHP framework. I discovered it while looking for a way to make Rails work ;-)

try Code Igniter as a simple yet well structured MVC application framework for PHP

For PHP, I have started using CodeIgniter which is a pretty light-weight MVC framework, and I highly recommend it. It's nice because it doesn't impose very many rules on you (unlike other frameworks) so you don't really have to modify your coding style much. Working with it feels like a framework should: just some stuff there to help you out, without getting in the way. Oh, and it has a great user manual (which is arguably the most important part when picking up a new framework).

For PHP, I have started using CodeIgniter which is a pretty light-weight MVC framework, and I highly recommend it. It's nice because it doesn't impose very many rules on you (unlike other frameworks) so you don't really have to modify your coding style much. Working with it feels like a framework should: just some stuff there to help you out, without getting in the way. Oh, and it has a great user manual (which is arguably the most important part when picking up a new framework).