Progress Chef
Ranked 4 of 5 configuration management tools by recommenders
Ruby-based configuration management tool that lets you fall back to plain Ruby when its DSL falls short. Critics say it is buggy and painful at scale.
Ruby-based configuration management tool that lets you fall back to plain Ruby when its DSL falls short. Critics say it is buggy and painful at scale.
21 people gave an opinion
- recommend it
- 10
- criticize it
- 11
- approval share
- 48%
Recommended in 7 of 13 months
- November 2025: not recommended
- December 2025: recommended
- January 2026: recommended
- February 2026: recommended
- March 2026: recommended
- April 2026: recommended
- May 2026: not recommended
- June 2026: not recommended
- July 2026: not recommended
- August 2026: recommended
- September 2026: not recommended
- October 2026: recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 10 people recommend itNeeds 10 or more, met.
- 0.9 recommenders for every criticNeeds 2 to 1 or better, not met.
- Recommended in 7 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Ruby DSL, drop into plain Ruby
“It was a Ruby DSL, which meant that anything the DSL couldn't do natively, you could just use Ruby right there.”
Comment from 17 Oct 2026 in “A skeptic's first contact with Kubernetes (2024)” “This is one of the reasons I liked Chef's DSL - it was Ruby.”
Comment from 25 Aug 2026 in “AI and Infrastructure Engineering”
What people warn about
Each mark is one comment
Buggy, poorly designed implementation
“Chef Software, especially after its acquisition, is just a dumpster fire of weird anti-patterns and seemingly incomplete, buggy implementations.”
Comment from 14 Nov 2025 in “Kubernetes Ingress Nginx is retiring” “I have early career trauma from someone's extremely unwise priority implementation”
Comment from 11 Dec 2025 in “Incomplete list of mistakes in the design of CSS” Legacy tooling kept around
“We just have Chef around because that's what was chosen 10 years ago.”
Comment from 30 Jun 2026 in “Looking Ahead to Postgres 19” “a lot of bad, not-so-gracefully aging tooling”
Comment from 14 Nov 2025 in “Kubernetes Ingress Nginx is retiring” “the Chef/Puppet soup before that”
Comment from 24 Apr 2026 in “I Am Building a Cloud” Painful beyond a handful of nodes
“Chef and even Ansible are much more painful for other reasons once you have more than a handful of nodes to manage.”
Comment from 14 Nov 2025 in “Kubernetes Ingress Nginx is retiring” “any moderate to large Chef installation always turned out to be such a nightmare in practice”
Comment from 4 May 2026 in “PyInfra 3.8.0 Is Out” Acquisition and vendor churn
“Chef Software, especially after its acquisition, is just a dumpster fire of weird anti-patterns and seemingly incomplete, buggy implementations.”
Comment from 14 Nov 2025 in “Kubernetes Ingress Nginx is retiring” “It has happened over and over, just look at Progress Chef, MongoDB, ElasticSearch, Redis, Terraform”
Comment from 13 Feb 2026 in “MinIO repository is no longer maintained”
Other configuration management tools people recommend
The four most recommended other configuration management tools, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
See all 5 configuration management tools, rankedWhat people said
21 of the 26 comments that mention it, newest first. Each links to the original comment.
“Chef, Piet, and Befunge are two favorites that spring to mind.”
“It was a Ruby DSL, which meant that anything the DSL couldn't do natively, you could just use Ruby right there.”
“I don't miss sshing into servers or using puppet, ansible, salt, chef.”
“This is one of the reasons I liked Chef's DSL - it was Ruby.”
“We just have Chef around because that's what was chosen 10 years ago.”
“any moderate to large Chef installation always turned out to be such a nightmare in practice”
“had previously been partially managed by Chef to ill effect”
“the Chef/Puppet soup before that”
“All of those other tools are complicated and fragile”
“Nix is just another chef, ansible, cfengine, apt, pacman”
“awful DSLs such as Salt, Puppet, Chef, etc.”
“It has happened over and over, just look at Progress Chef, MongoDB, ElasticSearch, Redis, Terraform”
“Author should explore Ansible/Puppet/Chef.”
“every one of which was designed to do systems administration at scale”
“I have early career trauma from someone's extremely unwise priority implementation”
“I feel like all Chef deployments grow an Ansible attachment eventually.”
“It’s a really dumb catch-22 design.”
“Chef and even Ansible are much more painful for other reasons once you have more than a handful of nodes to manage.”
“Chef Software, especially after its acquisition, is just a dumpster fire of weird anti-patterns and seemingly incomplete, buggy implementations.”
“a lot of bad, not-so-gracefully aging tooling”
“no more minutes to hours of fixing configuration management that never seems to work the first time”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.