Comments on: Rasmus Lerdorf: Web 2.0’s John Wayne

By: web.develop blog

web.develop blog — Fri, 03 Mar 2006 09:44:32 +0000

[…] (found in SitePoint’s PHP blog) […]

By: HarryF

HarryF — Thu, 02 Mar 2006 11:15:48 +0000

Harry, you are right to worry about using any $_SERVER variables like that, and it is a very good habit to get into to look suspiciously at uses like that. There are however $_SERVER variables that are safe. REQUEST_TIME is one of them. This is a variable filled in by PHP at request startup time. Even if for some odd reason you have register_globals turned on and you try to do ?_SERVER[REQUEST_TIME]=hack you can’t override it.

Thanks for the update.

By: xDest.com » Von keinem Framework zum Flamewar

xDest.com » Von keinem Framework zum Flamewar — Thu, 02 Mar 2006 09:25:45 +0000

[…] Auf der einen Seite wird sich mit den Sicherheitskonzepten beschäftigt, während auf dem Veröffentlichungs-Blog standepede die Schlacht zwischen Procedural-Programmierern und OOP Anhängern. Der Autor ist sich indes sicher, dass er nicht an den Auslöser der Waffe gekommen ist, die das Startsignal gab. What I was hoping to get across here is a simple example of how you can use PHP as-is, without additional complex external layers, to apply an MVC approach with clean and simple views and still have all the goodness of fancy Web 2.0 features. Trackback-URL: http://blog.xdest.com/archive/von-keinem-framework-zum-flamewar/trackback/ unquommentiert » […]

By: Rasmus

Rasmus — Thu, 02 Mar 2006 03:15:37 +0000

Harry, you are right to worry about using any $_SERVER variables like that, and it is a very good habit to get into to look suspiciously at uses like that. There are however $_SERVER variables that are safe. REQUEST_TIME is one of them. This is a variable filled in by PHP at request startup time. Even if for some odd reason you have register_globals turned on and you try to do ?_SERVER[REQUEST_TIME]=hack you can’t override it.

By: Rasmus

Rasmus — Thu, 02 Mar 2006 01:01:44 +0000

Jake, I don’t like “Web 2.0″ nor “AJAX” as terms any more than you do. Other words such as “blog” and “social media” are just as annoying, but I think the ship has sailed on us. These terms are here to stay and instead of spending half an article belabouring the point and coming up with alternatives that get the correct meaning across I just swallow the bile and move on.

By: Jake

Jake — Thu, 02 Mar 2006 00:18:42 +0000

Arrrggghhhhhhhhhhhhhhhhhhh ENOUGH with the cliche acronyms and terms already. AJAX, Web2.0, blah, blah, blah. Sad enough everyone else is adopting them, and now the godfather of PHP is? Sheesh. *Wipes brow*.

By: McGruff

McGruff — Thu, 02 Mar 2006 00:04:31 +0000

Er, I’d better qualify my earlier comment. When I first read the article what I picked up most was a strong anti-OOP message - using arguments about easy to read, modular code which are exactly those which I’d use to advocate OOP designs. However that may not have been what Rasmus intended. From his comments in the discussion, he seems to be arguing more against “monolithic” controllers rather than OOP itself - more in the original article comments section.

By: mrsmiley

mrsmiley — Wed, 01 Mar 2006 22:19:52 +0000

Should have read the rest of the article before posting before:

Try to avoid using include_once and require_once if possible. You are much better off using a straight include or require call, because the *_once() calls are very slow under an opcode cache. Sometimes there is no way around using these calls, but recognize that each one costs you an extra open() syscall and hash look up.

By: akrabat

akrabat — Wed, 01 Mar 2006 22:18:19 +0000

@soso:
ezComponents, Symfony and Solar are all deployed using Pear channels. I think you can safely assume that with the new channels feature, Pear deployment is the way forward.

I think that maintaining any application built on Symfony will be just like any other one.

I don’t know a lot about Java, but I bet that maintaining an app built using struts is different to one built using spring. Certainly, a TurboGears app is different to Django one in python-land. The difference with PHP is that there is no clear “leading framework” like Ruby’s Rails. Zend’s framework is the “hope” here, but atm it’s just vapourware.

By: mrsmiley

mrsmiley — Wed, 01 Mar 2006 22:14:48 +0000

Under speed issues, Rasmus mentions this:

Avoid include_once and require_once

Can anyone ellaborate on this on why these functions are slow? In comparison to what?