Posted by
michael
on from the choice-of-a-new-generation dept.
aftk2 writes "PHP.Net has just reported the release of PHP 4.3.0. The update sports a unified method of handling files and sockets, a bundled GD library (for working with images), and finalizes PHP's command line interface. For other information, check out the ChangeLog."
Is the friendly error messages, they point you back to the PHP Documentation. Being a regular in #PHP IRC channels, this is going to save me a lot of headaches:) Praise the lord, the newbies have fully automated RTFM messaging!!
-- I don't keep a lid on my coffee so when I walk around I look busy -me
Re:Best New Feature
by
netsharc
·
· Score: 3, Interesting
Hehe, you say it right, PHP is nowadays too popular that every "I know Frontpage!" idiot has begun trying it.
Yes I'm an elitist. Leave computing to the real guys.
-- What time is it/will be over there? Check with my iPhone app!
Re:consider running an opcode cache
by
MmmmAqua
·
· Score: 4, Interesting
Why no official PHP Opcode cache [weblogs.com]? 30-200% performance gain
Simply asked, simply answered: there is no "official" PHP opcode caching because PHP relies on the Zend engine and the PHP developers work very closely with the people at Zend, who sell the Zend Performance Suite (formerly Zend Accelerator), and the guys at PHP are not about to cut into Zend's livelihood by bundling a product with PHP which makes the Zend product redundant.
-- Arr! The laws of physics be a harsh mistress!
Re:consider running an opcode cache
by
glwtta
·
· Score: 3, Interesting
Just compiling PHP scripts on every page hit.
Ok, lets see, in the same thread there is a post about PHP not having an XML parser of any kind (the author mentions having to use regexp, insane as that sounds), I am assuming that means there is no HTML parser (or an equivalent of HTML::TreeBuilder at that) either.
Call this "informative-flame" bait, but I am trying to figure out why people get upset when PHP isn't refered to as the greatest thing of all time. I personally haven't used it for a couple of years, so I don't know about many of these features.
What does PHP use in terms of a browser agent (a la LWP)? Is there really no support simple filebased db persistence? (by which I mean something along the lines of tieing a hash to BerkleyDB). How well does it hook into the other stages of the Apache request handling pipeline?
Oh and something I'm curious about (too lazy to look it up, I guess) what sort of exception handling does PHP have (ie it's equivalent of 'try {} catch {} finally {}')?
What sort of logging modules are available? (log4PHP?) I'd also be curious to know about how PHP's templating systems measure up, from someone who's had experience with this sort of thing...
Anyway, this is a troll, but I am curious about the answers to those.
-- sic transit gloria mundi
Re:consider running an opcode cache
by
Kunta+Kinte
·
· Score: 3, Interesting
Simply asked, simply answered: there is no "official" PHP opcode caching because PHP relies on the Zend engine and the PHP developers work very closely with the people at Zend, who sell the Zend Performance Suite
That's the main answer I'm hearing. But zend is very expensive.
Maybe there's a compromise. How about a modest PHP opcode cache that has only some of zend's features; ie. a little bit slower and more conservative than zends.
I appreciate the work the zend guys have done, trust me I do. But that's an important feature to leave out.
-- Based on upvotes, Ageism is the only "-ism" Slashdotters care about and think isn't SJW
Slashdot Mirror
Is the friendly error messages , they point you back to the PHP Documentation. Being a regular in #PHP IRC channels, this is going to save me a lot of headaches :) Praise the lord, the newbies have fully automated RTFM messaging!!
I don't keep a lid on my coffee so when I walk around I look busy -me
Why no official PHP Opcode cache [weblogs.com]? 30-200% performance gain
Simply asked, simply answered: there is no "official" PHP opcode caching because PHP relies on the Zend engine and the PHP developers work very closely with the people at Zend, who sell the Zend Performance Suite (formerly Zend Accelerator), and the guys at PHP are not about to cut into Zend's livelihood by bundling a product with PHP which makes the Zend product redundant.
Arr! The laws of physics be a harsh mistress!
Ok, lets see, in the same thread there is a post about PHP not having an XML parser of any kind (the author mentions having to use regexp, insane as that sounds), I am assuming that means there is no HTML parser (or an equivalent of HTML::TreeBuilder at that) either.
Call this "informative-flame" bait, but I am trying to figure out why people get upset when PHP isn't refered to as the greatest thing of all time. I personally haven't used it for a couple of years, so I don't know about many of these features.
What does PHP use in terms of a browser agent (a la LWP)? Is there really no support simple filebased db persistence? (by which I mean something along the lines of tieing a hash to BerkleyDB). How well does it hook into the other stages of the Apache request handling pipeline?
Oh and something I'm curious about (too lazy to look it up, I guess) what sort of exception handling does PHP have (ie it's equivalent of 'try {} catch {} finally {}')?
What sort of logging modules are available? (log4PHP?) I'd also be curious to know about how PHP's templating systems measure up, from someone who's had experience with this sort of thing...
Anyway, this is a troll, but I am curious about the answers to those.
sic transit gloria mundi
That's the main answer I'm hearing. But zend is very expensive.
Maybe there's a compromise. How about a modest PHP opcode cache that has only some of zend's features; ie. a little bit slower and more conservative than zends.
I appreciate the work the zend guys have done, trust me I do. But that's an important feature to leave out.
Based on upvotes, Ageism is the only "-ism" Slashdotters care about and think isn't SJW