Link didn't work for me, but http://jburrows.wordpress.com/2011/12/05/what-to-look-for-in... did. Not sure why the date would have changed to earlier.
What to Look For in PHP 5.4
21–30 of 67 posts
Re: What to Look For in PHP 5.4
#22Earlier quoted context omitted.
These speed charts are why I would compile Php. http://naspinski.net/post/AspNet-vs-php--speed-comparison.as... It seems worth it too me. Thanks for the Yii link.
those charts don't say whether APC is enabled, which leads me to suspect that it isn't. APC is an opcode cache that greatly enhances php performance, no one runs a high traffic website without using APC
eAccelerator and XCache also do the same(ish) thing. APC usually helps way more on subsequent requests. While APC /can/ help a lot, it's not the magic speed bullet that some make it out to be -- if your app is a bodged mess of Joomla and stuff that you got outside developers to write for you, it'll probably still run like garbage with APC enabled.
Getting a bit off topic here, but one of the biggest performance killers I've seen is PHP devs writing Really Awful SQL(tm). Even beyond stuff like failing to use PDO and prepared queries to avoid SQL injections, if you look around you'll find tons of just really abysmal SQL. Typical problem: someone is using an oper in SQL that forces MySQL to not use indices. This absolutely kills performance and you typically won't notice it as a developer unless you're pre-populating your database with a large "real-world" dataset and doing proper performance testing.
Re: What to Look For in PHP 5.4
#23Earlier quoted context omitted.
Didn't downvote you, but 1) You're hijacking the thread with something unrelated and better suited for some online research or sites like SO 2) According to your questions you're not investigating PHP, you're looking for C# in disguise/in another set of clothes.
Yeah your probably right about asking this here. I was hoping for some Php experts maybe to point me in the right direction. I'm not trying to hate on Php just want to learn an open source framework or language that has similar features to C#. I really don't want to learn Java because I think thats a dead language. I'd rather use Mono but they don't have very good support for asp.net mvc.
Have a look at some jvm-based languages/frameworks. Grails/Groovy, and Rails with JRuby may be interesting to you. Both Groovy and JRuby have strong metaprogramming aspects, which may be of interest.
Heck, even Play! might change your mind about Java.
In the PHP world, there's a huge number of choices/options out there, and finding something that fits your style can be a challenge (because, until you know your style, you don't know what fits).
http://www.reddit.com/r/php would probably be a good place to ask these questions too.
Re: What to Look For in PHP 5.4
#24Closure::bindTo gives a nice js-like feeling, but i wonder why the hell a invocation of a closure in a class member triggers a warning.
Class/object members and methods do not share a "namespace", so it's possible to have a method and a member with the same name. If you assigned a closure to a member that had a colliding method, PHP wouldn't know which one to execute. I'm guessing this is at least some of the reason for that behaviour. You can force it to work in the absence of a collision by using a __call override. An example of which can be seen h…
Didn't think of that, pretty obvious now. ty :)
Re: What to Look For in PHP 5.4
#25Earlier quoted context omitted.
those charts don't say whether APC is enabled, which leads me to suspect that it isn't. APC is an opcode cache that greatly enhances php performance, no one runs a high traffic website without using APC
Did not know about APC...nice. Does APC just compile it after the first time and save it in memory? Can you use APC to create a packaged compiled file?
bytecode caches (like APC) store the bytecode on the fly in memory. you can't create somthing like a "binary" file.
edit: at least they're not intended to create "binaries". you can probably mess around with APC and make php look and behave like a compiled language. but you won't gain any notable speed improvements beyond the on the fly caching.
edit2: you can store php projects in a jar like file, caller phar. http://php.net/phar
Re: What to Look For in PHP 5.4
#26What to look for in PHP 5.4: 404 Not found.
I'm going to assume it's a backhanded insult and chuckle along.
Re: What to Look For in PHP 5.4
#27Has anyone tested the three opcode caches with the 5.4 release candidates?
I am depressed that eaccelerator seems to be fading away - they removed their shared memory functions for their build with 5.3 support.
In my experience eaccelerator is slightly faster and more stable than xcache. As a bonus, when it did have working shared memory functions (under php 5.2) it has session handler support so sessions are done completely in memory (added: without any additional code or modification)
Re: What to Look For in PHP 5.4
#28Nice to read something constructive and informative besides all the hate PHP has been getting lately.
What do you mean lately? PHP has gotten tons of well deserved criticism since it was created. It isn't "hate" to point out that a popular language is much worse than many other comparable languages.
When that "well deserved criticism" comes from the same people who feel compelled to post in every PHP thread, obsessively, over and over again ... it's hate.
Hate isn't inherently negative. You can hate evil, etc.
However, if you hate a programming language ... there's really something wrong with you. It suggests a very sheltered life. There are far more important things in life that deserve your hatred.
Re: What to Look For in PHP 5.4
#29Nice to read something constructive and informative besides all the hate PHP has been getting lately.
What do you mean lately? PHP has gotten tons of well deserved criticism since it was created. It isn't "hate" to point out that a popular language is much worse than many other comparable languages.
It becomes "hate" when the criticism is ill-informed and largely irrelevant. The bits of PHP that are "much worse" are mostly either legacy cruft that nobody in their right mind uses anymore, or bits are rarely touched in day to day programming but are safely wrapped in frameworks, ORM's, libraries etcetera.
Beyond that, PHP simply isn't particularly elegant (mostly since it was never really designed to be a programming language), and we all know it.
Other than that, I rarely see any relevant criticism, let alone constructive criticism.
Re: What to Look For in PHP 5.4
#30Earlier quoted context omitted.
What do you mean lately? PHP has gotten tons of well deserved criticism since it was created. It isn't "hate" to point out that a popular language is much worse than many other comparable languages.
When that "well deserved criticism" comes from the same people who feel compelled to post in every PHP thread, obsessively, over and over again ... it's hate. Hate isn't inherently negative. You can hate evil, etc. However, if you hate a programming language ... there's really something wrong with you. It suggests a very sheltered life. There are far more important things in life that deserve your hatred.
>When that "well deserved criticism" comes from the same people who feel compelled to post in every PHP thread, obsessively, over and over again ... it's hate.
No, you choose to label someone else's opinion as "hate" because it lets you dismiss it and throw out baseless insults at those people with less risk of getting taken to task for it. You told other people (theoretical people at that) what they think, and then told them there is something wrong with them and they lead sheltered lives. How incredibly arrogant.