Smarty - Yes or No?

i will not use Smarty nor will i ever consider it lol. I use my own template system that i have custom coded.

Against.

I prefer simple plugin systems. The more complex these engines get,t he more buggy they seem to get IMO.

Hi,

I am more of an end-user. Today I looked at a script that I was thinking of purchasing, and began to review the code. I noticed it was using Smarty, and I became a bit concerned, because I thought it added unnecessary complexity for the script that I was purchasing and additional potential points of failure that may occur over time. For this reason, I decided not to purchase the script.

From my perspective, if complexity is added to the on-going maintenance of an application (this is where most of the application cost is incurred), there should be a very good reason. Someone else mentioned that a templating system may be of value in a large project group. This may be true. However, there was a good counter example of how Wordpress manages the development of its ongoing development without the use of a templating system. I think this is one of the reasons it has been so successful.

Rich

I wouldn't use Smarty as my templating system, mainly because I am against templating systems that, I'm going to restate this, use their own home-grown language.

The use of one seems pointless to me when you can do the samething in the natural language. In addition to that, it slows the page load time way down.

I love Smarty, it's use of a cache on the database is great for large sites. (I am working on one learning it now).

Smarty is ridiculous, such a waste.

Originally Posted by Awesome Smarty is ridiculous, such a waste.

I agree.

Use M-V-C pattern. Much better!

Agreed, M-V-C is so widely used.

Well, smarty is MVC but it adds a whole extra layer to be parsed.

Originally Posted by Awesome Well, smarty is MVC but it adds a whole extra layer to be parsed.

which makes it slow and inefficient.