On Fri, 2006-08-04 at 17:23 -0300, Manuel Lemos wrote:
> Hello,
> 
> on 08/03/2006 02:53 PM Robert Cummings said the following:
> >>> The main thing in Manual's post that got me writing this in the first
> >>> place was :
> >>>
> >>> "Imagine if there would be only one PDBC (JDBC for PHP). Instead of that
> >>> we have a never ending choice of PHP database abstraction layers that
> >>> does not help newcoming developers that are lost and don't know what to
> >>> use."
> >> I admit I have not expressed myself clearly. What I meant is not that
> >> people should be disallowed to implement alternative APIs, but rather
> >> that they should not feel the need to do it.
> > 
> > I think you may be missing the point. Many people probably don't feel
> > the "need" to create an alternative API, they may just feel the desire
> > to do so. It's a great way to practice your skills, and in the end, you
> > have a nice API that meets your needs.
> 
> I do not think many people want to reinvent the wheel. Only those that
> feel forced to do it, because the alternatives are insufficient, will do
> it, only if they feel capable of doing it.
> 
> If there were consensual API specifications like in Java world, very few
> people would feel forced to reinvent the wheel.

I beg to differ. I think a good number of people really enjoy
re-inventing the wheel :)

Cheers,
Rob.
-- 
.------------------------------------------------------------.
| InterJinn Application Framework - http://www.interjinn.com |
:------------------------------------------------------------:
| An application and templating framework for PHP. Boasting  |
| a powerful, scalable system for accessing system services  |
| such as forms, properties, sessions, and caches. InterJinn |
| also provides an extremely flexible architecture for       |
| creating re-usable components quickly and easily.          |
`------------------------------------------------------------'

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to