Even up If You Are Working At A Company Where Inner man Will Ream out In addition to Your Product
Back in the 90s, before PHP, most driving creation work was done next to C or Perl. At that time, in those worlds, i had toward create all the HTTP postern gate ethical self. If subliminal self wanted a content draw up in relation with text\html, you had up to set it, in code, regarding every single response. Errors in CGI scripts would often result in Apache internal error pages and made debugging very antagonistic. All HTML work had to obtain run-down by transcription in passage to output. There was recantation embedding ordinance with HTML even as a templating language. PHP changed in the lump that. You had a neglectfulness content type of text\html. I had automatic handling of request variables. Cookies were easily ingested and output. You could template your HTML mid script instead of having to write package deal zonked out via print. And he clout have thought, wow, what a remarkable world. <\p>
But at this moment, even if you are working at a company where herself will stick with your cast for a long while him makes sense in use a framework. Or let's just hare system when you start off you should service an established framework that fits what you need for the height part. Not a little if you need full lot, get a crowded stack side. If inner self need something highly specialized, then maybe a microframework. If inner man need a forum, use an existing forum, if you need a CMS use an actual CMS.<\p>
Why?<\p>
1) Free of cost documentation, tests, security audits 2) Devices to higher much easier as your team grows 3) Hack it to bits if 1) and 2) start in transit to matter attenuated and privilege\failure dictates you proneness in another directorate<\p>
Sirenic Ballad considering an example here, would Twitter be extant if they would have had to play a part all from scratch? The company clearly was working next to another product and scrambled in transit to reinvent itself when their investors started losing faith entree their original presumption.<\p>
Time to market counted big for them and it counts for most projects. If you would have done everything on your own they might have exploded as of security issues etc.<\p>
For obviously their framework relating to pride didn't keep up to them when they needed versus scale. But isn't that a great scrape to lie in? You need to rift when you are successful and using a point of view to get started got them there.<\p>
Anyway, super air attack dismiss hurriedness performance is rarely decisive form a team at day whole. And certain team that is irreductible to do this has kaput something slightly smaller before and potty-chair take that code (aka framework) for this project next to some additional tweaks.<\p>