Comments on: Lazy PHP: Part 1

By: Jeremie

Jeremie — Wed, 22 Apr 2009 00:16:18 +0000

Spreading php code into many files can do more harm than good. Disk I/O is way slower than the time it takes to parse php into opcodes. It’s faster to include one file with 10k lines than 10 files with 1k lines, way faster. The real speed slowdown of PHP is when developers use tons of strings where integral values can be used, do not cache the result of pure functions, do not take advantage of the strict operators, use variable references within strings (that “hello $world” thing), etc.

By: Nathan Friedly

Nathan Friedly — Wed, 21 Nov 2007 21:57:22 +0000

You guys should update this article and replace the “to be continued” bit at the bottom with a link to part 2 so I don’t have to go back to google to find it.

By: kwastje

kwastje — Thu, 02 Mar 2006 13:07:30 +0000

For a beginner (medium), this lazy php approach is a very good tip when writing code. Tnx !

By: SitePoint Blogs » A pro-PHP Rant

SitePoint Blogs » A pro-PHP Rant — Tue, 21 Feb 2006 16:19:17 +0000

[...] Tried to explain the basics a long time ago here—the important thing to take from that (compared to mod_perl / mod_python / mod_* or even “X” application server.) is the interpreter returning to a fresh state after every request (no globals hanging around or otherwise). PHP really is shared nothing. You want scaling? Try here. [...]

By: SitePoint Blogs » The sysadmin view on “Why PHP”

SitePoint Blogs » The sysadmin view on “Why PHP” — Wed, 11 Jan 2006 14:29:06 +0000

[...] With PHP it’s very hard for a script to take down the runtime environment—the web server—I’d argue that you’d have to be deliberately trying to do so, perhaps filling up disk space or otherwise. Innocent mistakes, specific instances of runtime problems (e.g. script execution too long) and bugs remain local to specific requests and the PHP script handling them. On the next request, we begin again from scratch. [...]

By: HarryF

HarryF — Tue, 30 Nov 1999 00:00:00 +0000

Note: hopefully Sitepoint will fix the PHP formatting… not my fault honest

By: Octal

Octal — Tue, 30 Nov 1999 00:00:00 +0000

Nice tip. I like the use of the word 'lazy' rather than something along the lines of 'optimisation', quite apt for a person such as myself :)

As a side note this tip would also be helpful in other forms of OO programming not just PHP

By: HarryF

HarryF — Tue, 30 Nov 1999 00:00:00 +0000

“As a side note this tip would also be helpful in other forms of OO programming not just PHP”

Very true: there’s a number of pages on the C2 wiki about Laziness: http://c2.com/cgi/wiki?search=Lazy .

Think PHP’s case is a little special to the point where you need to use “eXtreme Laziness” because it dumps everything between requests – with compiled language that’s not the case and in most enviroments, memory tends to stay around for a little longer that 30 seconds.

By: Possibility

Possibility — Tue, 30 Nov 1999 00:00:00 +0000

So being lazy is a good thing? Great! :D

Really is true, though. I don't make those big scripts where you might have 101 functions, but it's never too early to start a good habit :)

By: Cam

Cam — Tue, 30 Nov 1999 00:00:00 +0000

Lol, "lazy" certainly attracted my attention ;) Also with PHP5 almost at RC quality, we shouldn't forget __autoload().

http://www.sitepoint.com/article/1192/10