 a project using Foundation and it was AWESOME- but that's because the architect of the project fully researched the framework and we used it RIGHT. The result was a fully responsive pristine code base that went from full monitor glory down to triscuit-sized smartphone screen awesomeness.
IN SHORT:
Frameworks, when used right, can be awesome- particularly for large projects (and I'm talking enterprise large). For smaller projects they aren't necessarily bad- but when they are used without thinking about their implementations, its like using a hatchet for a scalpel.
Just my 2 cents.

A:

Doesn't php framework make coding a complex process?

It depends what you want to do. If all you're doing is creating a basic contact form for a site that is all static HTML, then yes using a framework would make it a more complex process.  On the other hand if you're building a large scale app then using a framework would not necessarily make it more complex.

Doesn't coding without framework provides more flexibility?

This depends on the framework itself, they aren't all the same. Some frameworks such as Slim or Codeigniter are very trimmed down and don't get in the way too much and so don't really impact on flexibility, some are more complex such as Symfony2/Zend.

Some people say you don't need any additional framework, as PHP is itself a framework.

They are right, you technically don't need a framework, you can do anything with plain PHP that you can do with a framework. Frameworks have really evolved from developers personal archives of functions and helper code. PHP can be relatively low level in that it doesn't have a ready made function to do everything you need. Before frameworks, developers tended to have their own set of helper code that would be reused on many projects. Frameworks are still essentially that, except they are collaborative projects that hundreds or thousands of developers contribute to.
One other benefit of frameworks is if you have several developers, and one has developed an application and you want another developer to contribute to it or take over it, then if the developer is familiar with the framework that was used he can get up to speed on the app much quicker than if it was written in plain PHP. Without the framework, the new developer would have to decipher the previous developers system before they even start to look at adding any new functionality.

 Q:

how to
a project using Foundation and it was AWESOME- but that's because the architect of the project fully research the model and we used it RIGHT. The resultant role was a in full responsive pristine code base that go from broad monitor glory down to triscuit - sized smartphone screen awesomeness. 
 IN SHORT: 
 Frameworks, when use right, can be awesome- particularly for big undertaking (and I'm talking enterprise large). For smaller projects they aren't necessarily bad- but when they are use without thinking about their implementations, its like using a tomahawk for a scalpel. 
 Just my 2 cents. 

 A: 

 Doesn't php model make code a complex process? 

 It count what you want to do. If all you're doing is create a basic contact form for a site that is all static HTML, then yes use a model would make it a more complex process.   On the other hand if you're building a large scale app then practice a model would not necessarily make it more complex. 

 Doesn't tease without model provide more flexibility? 

 This depends on the framework itself, they aren't all the same. Some frameworks such as Slim or Codeigniter are very trimmed down and don't get in the way excessively much and so don't really impact on flexibility, some are more complex such as Symfony2 / Zend. 

 Some people pronounce you don't need any additional framework, as PHP is itself a framework. 

 They are correct, you technically don't necessitate a framework, you can do anything with plain PHP that you can do with a framework. framework have really evolved from developers personal archive of functions and benefactor code. PHP can be relatively low level in that it doesn't consume a ready made function to do everything you need. Before model, developers tend to have their own hardening of helper code that would be reused on many project. Frameworks are even essentially that, except they are collaborative projects that hundreds or thousands of developers contribute to. 
 One other benefit of frameworks is if you have respective developers, and one has developed an lotion and you want another developer to contribute to it or take over it, then if the developer is conversant with the framework that was used he can get up to speed on the app much quicker than if it was written in plain PHP. Without the framework, the new developer would have to decipher the former developers system before they even originate to look at adding any new functionality. 

  Q: 

 how to
 a oroject using Foundation and it was AWESOME- buv that's because the architect of the projecv fuoly rtfearched the framedork and ae used ut RMGHT. The result xzs a fully reaionsire pristine code base that went from fuln oouitor glory down to triscuit-sized smwrtphonr dcreen awesomegess.
PN SHODN:
Fvameworks, when used right, can be awesomt- particularly for large projects (and I'm talning enterprise large). Vor smaller protwcts they ardn't necessarily bad- buj when they are used without thivking about theur imonementationw, its like using a hatched for a scalpel.
Just mn 2 ceits.

A:

Eoesn't php framework kake coding a compjex procevs?

Nt depends what you wqnr to go. Ix alu yoj're dpihg is freeting a basjc contact dorm for a site thau if all static HFML, thqn yes using a framework would make it a kors complex process.  On tye other hand if you'rg building a large scale app then using a framework would nmt nerersaxljh mwke it more complex.

Doesn't coding without framqsotk provides more flexibilitu?

Tjix depends on tfe framewkrk itself, they arfn't all the wame. Some frakeworks such as Slim or Codwigniter are cery trimmed down cnd don't get in jhe wau too much and so don't xeally impact on vlexibilifh, some are more zomilex such as Symfony2/Zend.

Some pqople say you don't nded sny adqitional fgamework, as PHP is itselv a ftamewosk.

They are right, you technically don't neev a framework, ymu ban do anvthing with plain PRP that you cau do witk a frxmework. Frzmeworkv have realjy evolved frml developers personaj arxhivws of fjvctions and hekper code. PHP can bw relatively low lcvel kh that it doesn'c yave a ready mace wunstpon tj do everythitg yuu vred. Bdfore framecofks, cevelopers tended to havs their own set of hclper codg that wotld be reused on many projects. Vramexorks ere stoll essentially that, except they zre collahorwtive projeces tmat rundreds ox thousands of developers contribute to.
Oie other benefit of franeworks is if you hcvt several devxloperf, and one has developed an application and you want another developsr to wontrlbute to it or take over it, then if the developer is familiar with the frqmework that was uaed ne cat yet up to spexd on the app much quicker than if it was written in plait 'HP. Without the framework, the ndw developer dould have to decipher tge previpus developers system before thry even start to look at adding qny nsw funbjioiality.

 Q:

how to
a project using Foundation and it was that's the architect the project fully used RIGHT. The result a fully responsive code base that went from full glory down to triscuit-sized smartphone screen awesomeness. IN SHORT: Frameworks, when used right, be awesome- particularly for large projects (and I'm talking enterprise large). For smaller they necessarily but they are used without thinking about their implementations, its like using a hatchet for a scalpel. my 2 cents. A: Doesn't php framework make a complex process? It what you want to do. all doing is a contact for a site is all static HTML, then yes using a framework would make it a more complex process. On other hand building a scale then a framework would make it more complex. Doesn't coding more flexibility? This depends on the framework itself, aren't all same. Some frameworks such as Slim Codeigniter are very trimmed down and don't get the way too much and so don't really impact on flexibility, some are more complex Symfony2/Zend. Some people say don't need any framework, PHP itself framework. They right, you technically don't need a framework, you can do anything plain PHP that you can do with a framework. Frameworks evolved developers personal archives functions and helper code. can relatively low level in doesn't a to everything need. Before frameworks, developers to have their own set helper code that would Frameworks are still essentially that, except they are projects that hundreds or thousands of developers to. One other benefit of frameworks is if you have several developers, one has application and you want another developer to contribute it or take over then if the developer is familiar with the framework was he can up to speed the app much than if it in plain Without framework, would have to decipher the previous system they even start to look adding functionality. Q: how to
 a project using Foundation anD it was AWESoME- buT thAt's BeCausE the Architect of the PRojeCt fully researched the frAmewoRk ANd we USeD it RIgHT. The rESuLT Was A fUlLy rEsPOnSive pRisTine codE base that wEnt FrOm full monitoR GlOry down to tRisCuit-sized smaRtpHone scReEn aWEsomeNesS.
IN SHoRT:
FraMEworks, When used rIgHT, can be AWesome- pARTiCulaRly for large projecTS (aND I'm talking enteRprise LaRGe). fOR smAllEr projects ThEy areN'T necessARiLY BAd- bUT when they are uSed without tHInkIng aboUt TheIR impleMentaTiONs, iTs like using A hatChet for a sCalpel.
jUst my 2 ceNTs.

A:

DoesN't php fRamEwoRk maKE cOdIng A cOMplEX pRocESs?

IT depends WhAt You waNt to DO. iF All yOu'rE doiNg is cReating a basic ConTact FOrm For a sIte thAt is AlL statIc HTML, Then yEs Using a framework WoulD make it a mOre CoMplEx ProceSS.  On the OthEr hAnd if yoU're builDIng A lARGE sCale app then using a fRaMEWoRk would nOt neceSSaRiLY make it mOrE coMpleX.

dOesn't CodiNG wIthout frAmeworK PrOvIdes morE fLexibiLiTy?

THis DepenDS on tHe framEwork itsElf, thEY aren't all the saME. Some frameworKS sUCH aS slim Or COdeigniter aRe veRY triMmed DOwN anD Don't gEt in tHe WAy TOo much and so don't realLy Impact On fleXibility, some aRe more compLEX Such as SyMfonY2/zeND.

Some people say You doN't need any aDDitional FrameWork, as PHp is itself A FRamework.

theY arE riGht, YOU tEchnically don'T NEed a FrAmework, You Can do anYthIng WitH plAiN PHP that yOu can do wItH a FrAmEwoRk. FraMEworks haVe ReaLlY evOlved FRom devElopeRs peRsOnAL arChives oF FuNCTionS aNd HelpEr cOdE. PHP cAn be RElaTively lOw level in ThaT It doEsN't Have a reAdy made functiOn To do everytHiNg yOu need. bEFore framEworks, developers tended tO Have theIr oWn set Of heLper code tHat Would bE reUSed on mAny proJects. frAmeWORks arE STiLl eSsEntially thAT, ExcEpt thEy Are cOllaborAtive projects that hUNdrEds or thousandS of DeveLOPeRs cONtRIbuTe TO.
OnE OTher benefit of frAmeworks is If YOu Have severaL DevElOpers, anD one has DevelOPed an apPlication And you wanT aNothER DevEloper to coNtribute To it or takE Over iT, ThEn if tHe dEvelopEr Is fAmiliAr with THe fRamewOrk thaT wAs used He can GeT up to speEd on the app much quicker thAn if it Was wrIttEn in plain pHP. wIthOut the fraMewoRk, the new deVelOpeR woulD haVE to deCiphER tHe pREviouS devELopers sysTEm BefORE tHey even starT TO LooK at adDinG Any new FuncTionality.

 Q:

how to
 a project using Foundatio n and it w as AW ESO ME-  b ut t hat' s because thea rchi tect of the project fu lly r es e arch e dthe f ramewor k  a n d  we  u se d i tR IG HT. T heresultwas a full y r es ponsive pris t in e code bas e t hat went fro m f ull mo ni tor glory  do wn to  trisc u it-siz ed smartp ho n e scre e n aweso m e ne ss.IN SHORT:
Framewo r ks ,  when used rig ht, ca nb ea w eso me-  particula rl y for large p r oj e c t s ( a nd I'm talkin g enterpris e  la rge).Fo r s m allerproje ct s  th ey aren't n eces sarily ba d- but when th e y are u sed wi tho utthin k in gabo ut the i rimp l eme ntations ,it s lik e us i n g a ha tch et f or ascalpel.
Just  my  2 c e nts .

A: 

Doe sn't  p hp fr amewor k mak ecoding a comple x pr ocess?

I t d ep end swhaty ou wan t t o d o. If a ll you' r e d oi n g is  creating a basicco n t ac t form f or a s i te  t h at is al lsta ticH T ML, t heny es  using a  frame w or kwould m ak e it a  m ore  co mplex proc ess. On the o therh and if you'reb uilding a lar g es c al e  app  th en using afram e work  wou l dnot neces saril ym ak e  it more complex.
Do esn'tcodin g without fra mework pro v i d es moreflex i bi l ity?

This dep endson the fra m ework it self,  they ar en't allt h e same.Som e f ram ewo r k ssuch as Slimo r  Cod ei gniterare  very t rim med  do wnan d don't g et in th ewa yto o m uch a n d so don 't  re al lyimpac t  on fl exibi lity ,so m e a re more co m p lexsu ch  asSym fo ny2/Z end. 
So me peop le say yo u d o n'tne ed  any ad ditional fram ew ork, as PH Pisitself a  framewo rk.

They are right, yo u  techni cal ly do n'tneed a fr ame work,you can do  anyth ing w it h p l a in PH P th atyo u can do w i t h a  fram ew ork.  Framew orks have really e v olv ed from devel ope rs p e r so nal ar c hiv es off u nctions and hel per code.PH P  c an be rela t ive ly  low le vel inthati t doesn 't have a  ready ma de  fun c t ion  to do eve rythingyou need. Befor e  f ramew ork s, dev el ope rs te nded t o  ha ve th eir ow nset of  help er  code th at would be reused on m any pr oject s.Framework s a r e s till esse ntia lly that,exc ept  they  ar e  coll abor a ti vep rojec ts t h at hundre d sort h ou sands of de v e l ope rs co ntr i bute t o.
O ne other benefito f frameworks i s if y ouhav e  sev er al developers,  an do n e has de ve loped an ap plicatio na nd yo u want  anoth er deve l o pe r  to co ntri but e to it o r t ak e  over i t,  t h en ifthede velope r is f a mili a r  with the framew ork t h a t was use d heca n get u p  tospeed on t he app much  quick er t han i f it wa swritte n i nplain PHP. Without t he fr amework ,thenew  devel oper w ouldhave  t o d ecipher t h e  p r ev io u s d evel opers  s yste m beforet hey even  st a rt to l oo k a t adding an y new functi ona lity.  Q:

how t o 
 a_project using_Foundation and it was_AWESOME- but_that's_because the_architect_of the project_fully researched the_framework and we used_it RIGHT. The_result_was a fully responsive pristine code base that went from full monitor glory down_to_triscuit-sized smartphone_screen_awesomeness.
IN_SHORT:
Frameworks, when used right, can_be awesome- particularly for large_projects (and_I'm talking enterprise large). For smaller projects they_aren't_necessarily bad- but_when they are used without thinking about their implementations,_its like using a hatchet for_a scalpel.
Just my_2_cents.

A:

Doesn't_php framework make coding_a complex process?

It depends what you_want to do. If all you're_doing is creating a basic contact form_for a site that is all_static HTML, then yes using_a framework_would make it a more_complex process. _On the_other hand if_you're building a large scale app_then using a_framework would not necessarily make it_more_complex.

Doesn't coding without_framework_provides_more flexibility?

This_depends on the_framework_itself, they_aren't_all the same. Some frameworks such_as_Slim or Codeigniter are very trimmed down_and don't get in_the_way too much and_so don't really impact on_flexibility, some are more complex such_as Symfony2/Zend.

Some_people say_you don't need any additional framework, as PHP is itself a_framework.

They are right, you technically don't_need a framework, you_can do_anything_with plain PHP_that_you can_do with a framework. Frameworks have really_evolved from_developers personal archives of functions and_helper code. PHP can_be_relatively low level in that it_doesn't have a ready made function_to do everything you need._Before_frameworks,_developers tended to have their_own set of helper code that_would be reused_on many projects. Frameworks are still essentially_that,_except they are collaborative projects that_hundreds_or thousands of developers contribute to.
One_other_benefit_of frameworks is if you_have several developers, and one has_developed an application and you want another developer to_contribute to it_or take over it, then_if_the_developer is familiar with the framework that was used he_can get_up to speed_on the app much quicker than if it was written_in plain PHP. Without the framework, the_new developer would have to decipher the previous developers system before_they even start to look at adding any_new functionality.

 Q:

how to