I've used Ansible for over a decade, written probably a hundred roles most of which were used in production at large companies.
I honestly can't stand it anymore. The entire ethos of their opinionation is old, worn out, lazy.
An auto generated role from Galaxy init fails their own linter. This is fucking stupid.
One of the first major things golang fixed when it got big was directory structure requirements because everyone hates it. Ansible is doubling down on it.
@feld@SlicerDicer I was deep into chef around 2014-2015 but then chef the company started stretching themselves too thin and the community cook books suffered for it.
@feld@SlicerDicer I feel like the industry moved on from configuration management with things like k8s gaining so much traction and the "neo" way of doing things leaving these tools to rot
But nobody asks "who manages the back plane / system the runs the abstraction"
@SlicerDicer@feld yeah I've been doing this for about 12 years now - and all of the options now suck to a point that I have friends seriously considering developing a new configuration management tool.
Ansible is stuck in 2005, Salt is... weird, puppet was never good. My one coworker swears he'd rather write bash anymore than deal with the ansible ecosystem.
I mean FFS a galaxy init role doesn't pass ansible-lint. I feel like I am going crazy.
@SlicerDicer@feld I did a lot of work with Chef and even hung out with a few of the founders in the 2015 era. I just never felt the need to return to it, I saw some of the internal mess. I was at chef conf 2015 and saw them launch Chef Delivery at a time when we really needed chef to support cookbooks better rather than focus on a new product.
Add comment