Erika Heidi has posted the third part of her beginners guide to working with Puppet/Vagrant for development environments. In this latest post, she focuses on facts, conditionals and modules.

Finishing this guide to Vagrant and Puppet, I would like to show some advanced puppet resources. As I said before, Puppet is really powerful and extensive – I’m covering just the main concepts so you can have a good start point for creating your vagrant boxes.

She talks about the concepts behind facts first, pointing out that they're similar to variables, except that they're pre-defined. Conditionals let you do some basic logic and modules make it simpler to split up the functional pieces of the Puppet configuration into reusable chunks. She includes some code examples for these and how to set up your directory structure so you can create and use modules.

Getting a bit tired of those out there talking bad about PHP and comparing it to other languages, Kevin Schroeder decided to gather all of their complaints in one place and address them one by one.

Being a new Zender I've spent some time in the recent past looking at people's opinions about PHP now that it directly affects the work I do. In my research I have found a lot of interesting "opinions" about PHP vs. this that and the other thing, usually in the form of lists. "4 reasons why Java will outlast PHP", for example.

He lists five different things (like lacking features, slowness, and no serious applications written in it) and debunks each of them with facts, eliminating the FUD that has gathered around the topic.

Getting a bit tired of those out there talking bad about PHP and comparing it to other languages, Kevin Schroeder decided to gather all of their complaints in one place and address them one by one.

Being a new Zender I've spent some time in the recent past looking at people's opinions about PHP now that it directly affects the work I do. In my research I have found a lot of interesting "opinions" about PHP vs. this that and the other thing, usually in the form of lists. "4 reasons why Java will outlast PHP", for example.

He lists five different things (like lacking features, slowness, and no serious applications written in it) and debunks each of them with facts, eliminating the FUD that has gathered around the topic.

In his latest post, Wez Furlong responds to some of Jacob Santos' comments made earlier today about Service Data Objects (SDO).

I was just skimming over Santos' Post about SDO, and was saddened to see more anecdotes and less facts.

Specifically, he mentions two points - one dealing with the definition Jacob gave for the functionality and the other pointing out some better stats that Jscob didn't include in his comments.

In his latest post, Wez Furlong responds to some of Jacob Santos' comments made earlier today about Service Data Objects (SDO).

I was just skimming over Santos' Post about SDO, and was saddened to see more anecdotes and less facts.

Specifically, he mentions two points - one dealing with the definition Jacob gave for the functionality and the other pointing out some better stats that Jscob didn't include in his comments.

Wez Furlong posts today about a response made to a previous mention of "PHP vs. ASP.NET" in this article from Joe Stagner in this post on his MSDN blog.

From Wez:

Wez also mentions one of his personal views on the whole debate, basically saying that even if PHP is the faster/more efficient, some situations might do better with an ASP.NET solution (what's the cost of implementation?).

Wez Furlong posts today about a response made to a previous mention of "PHP vs. ASP.NET" in this article from Joe Stagner in this post on his MSDN blog.

From Wez:

Wez also mentions one of his personal views on the whole debate, basically saying that even if PHP is the faster/more efficient, some situations might do better with an ASP.NET solution (what's the cost of implementation?).