In his latest blog post, Pádraic Brady talks about a "sweeter alternative" to using Smarty for your site's templating - Template Lite.

Use the term Template Engine in a PHP forum and the word "Smarty" will inevitably crop up. I like Smarty but, similar to a few PHP libraries, it's very bloated.

I try to keep my applications lean and mean - small, fast, and adaptable. Unfortunately, Smarty disagrees with my needs. It's bloated design while packing a mighty punch, uses a chunk of memory and processor time I dislike. Since I also develop open source apps which end up on shared hosts, my concerns are even more justified.

Enter Mark Dickenson. Mark is the developer of a Smarty alternative: Template Lite.

He talks about what Template Lite is and what kinds of advantages it has over Smarty, including staying try to its name. Pádraic measures it as not only being faster but also having 50% of the memoery footprint that Smarty does. He seems to favor it for those places when he just needs something light and easy on a site.

In his latest blog post, Pádraic Brady talks about a "sweeter alternative" to using Smarty for your site's templating - Template Lite.

Use the term Template Engine in a PHP forum and the word "Smarty" will inevitably crop up. I like Smarty but, similar to a few PHP libraries, it's very bloated.

I try to keep my applications lean and mean - small, fast, and adaptable. Unfortunately, Smarty disagrees with my needs. It's bloated design while packing a mighty punch, uses a chunk of memory and processor time I dislike. Since I also develop open source apps which end up on shared hosts, my concerns are even more justified.

Enter Mark Dickenson. Mark is the developer of a Smarty alternative: Template Lite.

He talks about what Template Lite is and what kinds of advantages it has over Smarty, including staying try to its name. Pádraic measures it as not only being faster but also having 50% of the memoery footprint that Smarty does. He seems to favor it for those places when he just needs something light and easy on a site.

In one of his latest posts, Marcus Whitney looks at the upcoming year and what the future holds for mobile applications - and where PHP might fit into it (with a little help from Flash Lite).

Since meeting with Jackson for lunch this week, I am definitely convnced that he is on to something when he says 2006 is going to be huge for mobile. Here's another challenge to the PHP community. Flash Lite is pretty cool. So.. I'm pretty excited by Flash Lite, and the announcement that Samsung phones will support it is good news for me and all the Sprint/Nextel/Embarq customers out there.

Any chance us PHP devs will be able to start writing robust mobile apps? Maybe working in tandem wiith the beauty of Flash on the front end?

It'd be interesting to see if this line of thought would lead to any major PHP/Flash applications. The possibility is definitely there with its ability to not only import data like XML, but pull in other resources as well...

In one of his latest posts, Marcus Whitney looks at the upcoming year and what the future holds for mobile applications - and where PHP might fit into it (with a little help from Flash Lite).

Since meeting with Jackson for lunch this week, I am definitely convnced that he is on to something when he says 2006 is going to be huge for mobile. Here's another challenge to the PHP community. Flash Lite is pretty cool. So.. I'm pretty excited by Flash Lite, and the announcement that Samsung phones will support it is good news for me and all the Sprint/Nextel/Embarq customers out there.

Any chance us PHP devs will be able to start writing robust mobile apps? Maybe working in tandem wiith the beauty of Flash on the front end?

It'd be interesting to see if this line of thought would lead to any major PHP/Flash applications. The possibility is definitely there with its ability to not only import data like XML, but pull in other resources as well...