On Sat, February 2, 2008 2:14 pm, Steph Fox wrote: > 2) Maintenance status needs to be part of the equation. > > 3) Stability needs to be part of the equation. > > 4) Appropriateness to a given PHP branch needs to be part of the > equation. > > 5) CS and documentation need to be part of the equation. > > Thoughts?
It seems to me that broad classifications of common usage patterns might be part of the equation. A shared hosting setup and a distributed server farm and a dev setup might all have different recommended extensions, no? Sure, somebody setting up a shared host or distributed server farm SHOULD do their research and figure out what should/shouldn't be in there, but the PHP Dev Team could probably knock up a "starter list" and save them a great deal of time... -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some indie artist. http://cdbaby.com/from/lynch Yeah, I get a buck. So? -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
