Posted by Jim Michaels on 03/02/06 23:04

"J" <notanymore> wrote in message
news:PoCdnWNmid4Da2nenZ2dnUVZ_s-dnZ2d@adelphia.com...
>
> "NC" <nc@iname.com> wrote in message
> news:1140057031.204786.34080@g44g2000cwa.googlegroups.com...
> J wrote:
>> > > > PEAR:db would be a good PHP example.
>> > >
>> > > Yeah, it's a start ;)
>> >
>> > Nope, it's a dead end... Lots of completely avoidable overhead in an
>> > effort to (supposedly) speed up development...
>> >
>>
>> There's a block, where's the parry? Do you have an alternate suggestion?
>>
>> "Write your own code..." I'm expecting..
>
> You write your own code regardless of whether you use an abstraction
> layer or not. The amount of code you have to write is approximately
> the same regardless of whether you use an abstraction layer or not; you
> still issue commands for connecting to a DB server, choosing a DB,
> running queries, and fetching their results. The difference is how
> fast it happens and how much system resources get consumed in the
> proces. Last times folks at phpLens tested it, PEAR:db had an overhead
> of 150-170%:

A CAD/CAE company I know of decided to go OOP with their code. it also got
bloated and ran slower.
If you are looking for event-driven architecture, it's hard not to go that
route though.



>
> http://phplens.com/lens/adodb/
>
> Cheers,
> NC
> //END CONTEXT
> ********
>
> Thanks for the reply. Those benchmarks are interesting. Is it PEAR
> itself,
> or just a biproduct of OO design i.e. lots of classes to create, more
> function calls, etc?
>
> Thanks!
> -JB
>
>

[Back to original message]