On March 19, 2004 06:19 pm, Rasmus Lerdorf wrote: > This is also not the argument here. How many times have you heard me say > that this should not be PHP's problem? It is architecturally incorrect to > fix this problem in PHP and it can never be done correctly. However, PHP > is also the pragmatic solution to the web problem and until such a time > when someone else decides to actually fix this, we have to address it. > And I completely don't buy the "improving our hacks prevents development > of a real solution" argument. If we were talking about the same > developers working on both, or even if there was a clear way to solve the > actual problem that argument might have some weight, but it isn't the same > developers nor is there a straightforward way to solve this just looking > for someone to sit down and write the code.
Once PHP begins (already did I suppose) implementing these hacks we'll just have more and more people convinced that this is a PHP issue and push for further hacks on top of the existing ones. Between adding these hacks and fixing various bugs resultant from these hacks or various bypasses of these 'security' measures much developer time (better spent elsewhere) is wasted. Before this discussion goes even further let me just summarize my position: -1 Ilia -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
