[UPHPU] notes from austin php users group

[Jacob Wright]

>
> > It's not what PHP needs, it's what companies/developers need.
> > Especially in a climate where excellent programmers are few and far
> > between.  Thus, good frameworks speed development, ensure standards,
> > reduce errors, and reduce maintenance.
> >
> > I guess it depends on your personal definition of the word
> > 'framework'.  To me, it's come to symbolize a bloated, overextended
> > set of tools that often imitates the authors' personal preferred
> > language's (Java, C++, etc) that often detract usage or hide
> > features of the native language.
>
> Yeah, that's how.... wait. No, that's not it.
>
> By framework, I mean a pile of code that comprises all the stuff you
> need to put in 90% of the applications you build - thus enabling you
> to cut to the chase rather than reinventing the wheel each time you
> sit down to a new project. Well, that, and the code is tested by
> thousands of people on varied environments, many of which contribute
> free code and ideas to the said pile of code.


I have to say there were many bloated frameworks that came out when
frameworks first started becoming popular in PHP. They had large XML
configuration files like Java, their database abstraction layers were just
like Java's JDBC. But now with frameworks out like CakePHP (John's framework
of choice) you can work with something easier.

> Of course, if you mean 'a collection of libraries utilized for one
> > specific purpose', then I certainly agree.
>
> libraries != framework (re: Zend "Framework")


Agreed. The Zend Framework, if used as a framework, comes in dead last when
benchmarked with others.
http://paul-m-jones.com/blog/?p=236

> Of course, extracting and removing boilerplate code, custom
> > exceptions / error handling, automation, and sometimes unit testing
> > is par for the course for any good development team. And, often,
> > internally developed (if done correctly) frameworks will result in
> > just as much (if not more!) reduced development time, debugging,
> > maintenance while ensuring standards.  Also, you don't have to deal
> > with learning Yet Another Framework (tm), which can be just as hard
> > as learning a new language (and counterintuitive to good said
> > language's developers).
>
> I don't mind internal frameworks or libraries, though they miss out
> on community based advantages (free code, free testing).


There's nothing like working with your own code with the interface and
features you like best. I have my own framework that I use. But then again,
teaching others how to use it is boring and writing documentation for it
even more so. And it is a TON of work.

I'm missing out on the community's advantages of course, and would like to
try and learn to love other peoples' code. :) I just don't know how to fit
into and open source community. Never tried before.

-- 
Jacob Wright
Within Code LLC