> At 23:11 09/12/2002, Frank M. Kromann wrote: > >> > >> Please mention the name change at least in the NEWS file and maybe > >php-cli > >> could even output a readable error when beeing called as cgi. > > > >These are good points. > > I think that's a bit like inventing problems and then trying to fix them. > Let's keep it down to things we can determine relatively easily: > > - Nothing bad will happen if we name the new CLI with whatever kind of name > - php-cli, phpsh, whatever > - There WILL be some level of confusion if we rename the CGI binary > > If we use this KISS approach, why the heck are we even considering this > rename? >
I happen to agree with Zeev here - I won't argue the potential of using PHP for GTK/command line scripting, however, currently that is not PHP's target audience, and in my opinion we should focus on our target audience first. Should PHP progress and become more popular outside the webspace (and cgi becomes less popular as well :), then it would make sense to rechange the name (perhaps for PHPv5), but at this point changing it to php-cgi just seems like solving a problem by creating a bigger one. -Sterling > Zeev > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, visit: http://www.php.net/unsub.php > -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
