hmm i use scripted languages because i prefer and they allow/force simple-to-read-code. but that does not mean a scripted language can't evolve to expose "complicated" code constructs like multi-threading and daemon-building in a simple manner too. i'd prefer it if a language like PHP can be used for other things besides webserving too. i also think at least some web-apps could benefit from multi-threading and daemon-building.. particularly web-apps that deal with real-time dataflows. and btw, the distinction between compiled and scripted is not a hard one anymore eh.. not with zend and that facebook php-compiler out there. On Tue, Mar 23, 2010 at 10:04 AM, Per Jessen <per@xxxxxxxxxxxx> wrote: > Daevid Vincent wrote: > >> I've been using PHP for a decade or so (since PHP/FI) and love it. The >> one problem that seems to always keep coming back on enterprise level >> projects is the lack of threading. This always means we have to write >> some back-end code in Ruby or Java or C/C++ and some hacky database >> layer or DBUS or something to communicate with PHP. > > Use the right tool for the right job - PHP is a scripting/interpreted > language, it does not need threading (IMO of course). > > > -- > Per Jessen, Zürich (9.4°C) > > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
