<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Chef on Danilo Falcão da Silva</title><link>https://falcao.org/tags/chef/</link><description>Recent content in Chef on Danilo Falcão da Silva</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 22 May 2026 09:00:00 -0300</lastBuildDate><atom:link href="https://falcao.org/tags/chef/index.xml" rel="self" type="application/rss+xml"/><item><title>Ansible, Puppet, Chef and SaltStack: Why Ansible Is Still My Default in 2026</title><link>https://falcao.org/posts/ansible-puppet-chef-saltstack-2026/</link><pubDate>Fri, 22 May 2026 09:00:00 -0300</pubDate><guid>https://falcao.org/posts/ansible-puppet-chef-saltstack-2026/</guid><description>&lt;p>There are four names that come up when you ask how to manage
configuration at scale. I&amp;rsquo;ve used all four, in production, over the
last fifteen years. The answer to &amp;ldquo;which one&amp;rdquo; is not the one that
wins benchmarks — it&amp;rsquo;s the one that matches how your team thinks
about change.&lt;/p>
&lt;p>The shortlist hasn&amp;rsquo;t changed since the early 2010s: &lt;strong>Ansible&lt;/strong>,
&lt;strong>Puppet&lt;/strong>, &lt;strong>Chef&lt;/strong>, &lt;strong>SaltStack&lt;/strong>. The ownership has changed. The
licences have changed. The community gravity has very much changed.
Ansible sits at &lt;strong>31.94%&lt;/strong> market share for new projects as of early
2026 and is, by a wide margin, the most-adopted tool for new
configuration-management work. Puppet holds &lt;strong>12.41%&lt;/strong>, Chef around
&lt;strong>6.70%&lt;/strong>, and Salt has fallen out of the top-tier mindshare entirely
even though the codebase is still actively developed under Broadcom.&lt;/p></description></item></channel></rss>