Re: [binarycloud-dev] Re: [PEAR-DEV] Re: [metabase-dev] RE: [PEAR-DEV] New Metabase Aniversary release

> Why can it only benefit from having only one DB abstraction > package? Why can't it also benefit if there are many DB > abstraction packages? If you have ever been involved in a large software project with any language you will realize why JDBC for Java is a good idea. Interoperability is a problem throughout computing, and anyone with experience building software will tell you that interoperability is an important issue. With multiple database abstraction packages, interoperability is a problem. If all of the _many_ high quality, opensource PHP applications use some common standards, including and especially a common database abstraction layer, the PHP community will grow and mature as a result - which is good for us all. If you read reviews in magazines where ColdFusion, ASP, JSP, Perl, and PHP are compared, you will see that (rightly) the platform is criticized for its lack of database abstraction. It is a real problem. I commend Stig and any others who have encouraged this effort. It's great to see this happen and I think it will benefit us all. I actually believe the best solution would be to do a C port of the PEARized version of Metabase so it was compiled into the engine, and to see the other database functions deprecated as of PHP 4.2 or 5. I think Stig once talked about doing a C port of PEAR DB and putting it in the engine... if that was based on PEARized Metabase I'd be freakin' ecstatic :) In any case, quantity is not better than quality in this case. We should endeavor to create the highest quality package that will satisfy _everyone's_ needs, and use that as the standard database abstraction package for PHP. best, _alex