RE: [phplib] [RFC] Future of phplib From: Alan T. Miller (amiller <email protected>)
Date: 07/21/01

Bertrand,

> I don't see why development with PHPLIB could not be done using also PEAR
> classes to manage special functionality. I use PHPLIB with other PEAR
> classes all the time.

I think it can be done at the same time, it is just that it seems a little
awkward to the uninitiated like myself. If we are targeting the PHPLib
framework to the web developer such as myself (of course we may or may not
be), the idea of jumping in and figuring out the ins and outs of both PEAR
and PHPLib, seem a daunting task. The benefit of having one system, one set
of standards sounds much more appealing to a web developer such as myself.
With the increasing value of PEAR in the near future, there will simply be a
lot of people such as myself, who might overlook or simply not bother with
PHPLib, and even be more inclined to work with what may be a more clunky or
less functional class in PEAR simply because overall, it seems easier to
contend with than learning two systems.

> The future is neither in PEAR or PHPLIB, it is where we put our efforts.
> There is a place for both PEAR and PHPLIB, it is just a matter of
> positioning. PEAR : heavyweight, powerful but slower - PHPLIB : easier,
> faster but not as complete.

This may be true, but it is no secret that UNIX was always the better
operating system, or even Mac OS when compared with MS DOS, but it was the
utility of DOS that won it out in the end and pushed a consumer computer
revolution, which in turn has taken us all much further. I think it is
inevitable that PEAR will become a much bigger force and people will look
towards PEAR for what they might have looked for in something like PHPLib.

My own experience with PHPlib in the beginning was a frustrating one as I
tried to implement it when I was just learning what a variable was... I must
admit, it scared me away for a little while. However, PEAR has been working
on creating a system whereby installing PEAR and its "modules" will be very
simple, and as a result PEAR will be VERY attractive. This move in itself,
with its close integration into PHP, will make PEAR the defining force in
the future of PHP.

While we may think of PEAR now as a big system, my own personal preference
is to learn the system that will benefit me most, if I can get an unlimited
number of useful functionality out of PEAR, verses a limited set out of
PHPLib, I, as well as many other would be inclined to just learn the big
system (especially if it was actually easier to set up etc).

Of course the last point I would make towards PEAR being a "Big" system, is
that hardware is something that is always getting cheaper, and better.

Alan 

-- 
Abbestellen mit Mail an:   phplib-unsubscribe <email protected>
Kommandoliste mit Mail an: phplib-help <email protected>