Perhaps by adding it to core the original reasons for alternatives will be reduced and the things that make those special could be implemented into apc?
On Jun 20, 2010, at 1:56 PM, Ferenc Kovacs <i...@tyrael.hu> wrote: > On Sun, Jun 20, 2010 at 10:39 PM, Lukas Kahwe Smith > <m...@pooteeweet.org>wrote: > >> >> On 20.06.2010, at 22:21, Lester Caine wrote: >> >>> ( Foregot to change address again :( ) >>> Ilia Alshanetsky wrote: >>>> What are your views on including APC in the core, or reasons not to? >>> >>> Dictatorship? >>> Optional module which have well used alternatives should not be proced on >> by default! Probably more people use alternatives and have for years? >> >> >> probably not actually .. my guess is that the vast majority of users do not >> use any byte code cache today. this could be our effort to reduce co2 >> emissions world wide. >> > > Are you sure? > Usually installing an opcode cache is the first optimalization effort for > every php project. > I'ts easy, it's transparent, and can give a vast amount of performance > boost, so > - shared hosting providers install it, because they can oversell more > - ppl who can run dedicated server/vps usually knowledgeable enough to > install it right away > > > >> >> +1 on adding apc to trunk >> +0 about enabling apc by default .. or rather undecided at this point. >> >> > I prefer xcache, but I think that its better adding apc to the core, than > nothing at all. > Why should this be disabled by default? > > I never had any problem using xcache. Maybe that it has no gain if you only > use php for cli or cgi. > > Tyrael -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
