James Crane wrote:
I've written a short paper on the future of PHP and I'd appreciate it
if you folks would take a look at it and exchange your thoughts with
me.
http://www.maraby.com/papers/pushing_php_into_the_web_20_generation
Don't be too skeptical. ;)
Not being funny, but the one thing you seem to suggest is "everything as
objects within php" - Quite aside from totally disagreeing with your
logic in this, I don't see the point. One of the strengths of php is
that it can be used both as a procedural and OO language (or anywhere
inbetween) - what you're arguing for can all be accomplished within
userspace.
I really dont' get what you're trying to achieve with this - maybe I've
just totally missed the point, but just saying that PHP is blind to
inherent dangers without saying either why they are dangers or in what
way php is blind to them doesn't do anything to convince me that this is
anything more than your personal preference on how you would like to see
the language working.
"web2.0" or whatever is afterall, bloody hard to impliment in a
real-world situation when dealing with corporate clients. Fine for home
users but it's all high-level client side stuff like javascript doing
the real interface stuff. Given that loads of corporations outright ban
javascript, this causes quite a problem. I don't see why php needs to do
anything on this front really, it's a userspace issue.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
