At 2:28 AM +0100 6/10/09, Michael wrote:
The standard PHP execution model is geared almost exclusively
towards web-used (though crons etc. are reasonable)... that is, to
sit in/with a server and handle requests... to operate over, at
maximum, "insane" lifespans of 30 seconds.
There are languages designed to be used for desktop programming, and
for various tasks in general. The smart thing would be to use them.
PHP may be a hammer, but every problem is not a nail.
Use the tools designed for the job.
I've written many different desktop apps that wrap routines from
other languages and/or use applications that are just below the
surface (for example, a desktop apps that uses an Unix app). If you
can do it, it sure beats rewriting everything in one language.
Plus, I have also written desktop apps that interface with php
scripts to do web stuff -- that's not difficult.
So, I don't think it's too much a stretch of the imagination to think
there might be a php environment that could create a desktop
application to do web work.
Beside, this is how languages evolve. There is no job that any tool
is designed for. The "job" is our current perception of the task at
hand and that is always changing.
Think about it -- why are all languages are looking more and more
alike? Why is it that you can jump from versions of BASIC to C, C++,
completely foreign environment? You think that's by design? Or is
there something else going on?
Perhaps what's going on it that these languages are expanding and
adapting to the task at hand (the job) as perceived by countless
programmer working in different environments. Usually, there is one
most logical way to solve any problem. We all shoot at the target and
it should come to no surprise that our shots are grouped around a
http://sperling.com http://ancientstones.com http://earthstones.com
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php