Digital Sandwich

Heh, I'm probably going to get lambasted for this...but I'm going to step out and say dreamweaver templates suck! Now don't get me wrong, they are very handy and they do limit the amount of time it take to make sitewide changes to global elements...but when you have a large site, they are just plain annoying. For instance, I now get to spend about 1 hour downloading pages of the site just so I can make 1 little navigation change. Then I get to spend another hour uploading them. Chances are my connection will be dropped at least twice so I will have to baby sit the stupid download/upload process.

Life would be so much easier if we just used a severside templating solution. You know, macromedia would make so many people happy (specifically programmers) if they just gave us a perl script that would update all files using a template in a site on the server. It would also save lots and lots of otherwise waisted bandwidth.

I was doing my daily browsing of the sitepoint forums and was visiting a topic we have started regarding Hibernate and OQL. One of the posts in that topic said pretty much the following:



Now I don't exactly know what the "PHP" way is. But a statement like this makes ABSOLUTELY no sense to me. I decided against posting my thoughts at sitepoint as this would undoubtedly ruin an otherwise informative thread.

Now thankfully I was able to get a better idea of where this guy was coming from since he posted a comment at the following blog post:

http://blog.thinkphp.de/archives/14-ReflectionClasshasMethod.html.

Read on....