Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If you choose using a framework, Not depending on which one you'll chose, the first thing you have to know is that : </p> <ul> <li>it'll take some time for you to know it</li> <li>you'll do crapping things, during that time ^^</li> <li>so, take into account the fact it'll take some time before you are fully operational <strong>:-)</strong></li> </ul> <p>I think those points are the most under-estimated points : using a framework takes not much time... Using it well and to the full extend of its abilities takes... Well, a couple of months, maybe... Which means, when you are at the end of your project you'll say "I should rewrite that with all the stuff I learned while re-writing it the first time" :-D</p> <p>What it means is : <strong>learn what the framework can do, learn how to use it, and use it for a while on small applications, before starting rewriting your big one !</strong></p> <p><em>(Disclaimer : this previous paragraph was a re-post of a part of an answer I did to <a href="https://stackoverflow.com/questions/1234858/rewriting-a-php-app-in-cakephp">this question</a>)</em></p> <p><br> On the other side, if you don't use a framework :</p> <ul> <li>it will still take time to know PHP well enough to develop your application</li> <li>you will still do crapy things during that time ^^</li> <li>and you should still spend some time on "little projects/applications" before starting programming the big one, to get familiar with the language.</li> </ul> <p>So, actually, using a framework or not, the same stuff is still true : using a framework only gets you some boundaries, help, and pointers -- and a lot of already existing great code !</p> <p><br> Finally, about the question of "<em>using a framework</em>" vs "<em>not using a framework</em>"... Well, it's 2009, and considering the amount of things/code/best-practices/guides/whatever a framework brings, I'd definitly go with a framework : I work in a company that develops websites, and we don't ever ask ourselves the question "<em>should we go with a framework</em>" -- we still go with the question "<em>which framework is the best for this project</em>", though.</p> <p>Plus, if you are willing to work <em>(ie, professionnally speaking)</em> in PHP development, having used a "big" framework would be a plus on your resume <em>(well, I don't know about the country where you're from, but, in France, it is definitly a plus)</em></p> <p><em>(Added as an edit, to be more clear about what I meant)</em> <br>Still, while I'd say "<em>use a framework</em>" for your application, that definitly doesn't prevent you from first spending/investing some time learning at least the basics of PHP, it's syntax, and some of it's gotchas -- but that could be on smaller "example applications", I believe.</p> <p><br> And, if you are curious about "<em>which framework should I choose</em>"... Well, that's quite a debate ^^ <br>About that, instead of debating all over again, here are a few pointers to other questions/answers :</p> <ul> <li><a href="https://stackoverflow.com/questions/817096/to-use-a-php-framework-or-not">To use a PHP framework or not?</a></li> <li><a href="https://stackoverflow.com/questions/1046091/which-php-framework-is-right-for-this-project">Which PHP Framework is right for this project?</a></li> <li><a href="https://stackoverflow.com/questions/279003/why-do-i-need-to-use-a-popular-framework">Why do I need to use a popular framework?</a></li> <li><a href="https://stackoverflow.com/questions/2648/what-php-framework-would-you-choose-for-a-new-application-and-why">What PHP framework would you choose for a new application and why?</a></li> </ul> <p><em>(Well, how strange is that : some of those might also help you answer your own question ;-) )</em></p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload