Re: Proposing a new extension : Autoload

> I think SRM is a bad idea, it is against everything that PHP is not > meant for. THe strength of PHP is it's huge potentional for scalability. > A solution like SRM just adds a single point of failure and a bottle You don't have to have a single installation... and I thought you wrote it... > neck. In situations where speed actually matters this is possibly the > worst architecture you can pick. > The strength of PHP is it's huge potential for scalability? Yah but if something needs more hardware because it can't efficiently reuse things it's already processed that's an awful lot of unnecessary scaling. Why do people feel the need to rewrite things in C? One reason is Because comparatively they'd need a lot more hardware to do the same job as fast... > However, this has all totally nothing to do with includes being slow. As > a matter of fact, I find that statement as-is hugely uneducated as there > is no benchmark to prove anything like this. > I said... include_once, require_once's are slow, and I mentioned why... > > So why don't we truly share the knowledge... and help to find a > > solution for the root problem... > > The root of the problem is people blabbering about stuff they have > little clue about. > That's really, not the case with me... > regards, > Derick > > -- > Derick Rethans > http://derickrethans.nl | > http://ezcomponents.org | > http://xdebug.org > > -- > > PECL development discussion Mailing List (http://pecl.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- ~ Pedram Nimreezi Senior Programmer / Frameworkologist mc@majorcomputing.com | pedram@5g.com -- "A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools." - Douglas Adams