[chef-dev] Re: Re: Re: Re: Dialect support and loading enhancements

[Noah Kantrowitz < >]

On Sep 20, 2013, at 2:51 AM, Avishai Ish-Shalom 
<
 >
 wrote:

> To me Chef's biggest power was its flexibility; i can easily monkey 
> patch/wrap whatever cookbook/internal chef behavior, and i'm not the only 
> doing this. just look at the number of cookbook that use rubygems or 
> include internal chef mixins.

It is worth noting that at least with the dialects I've written so far, this 
would continue to work just fine. The JSON/Yaml attributes loading just calls 
the same things you would to set the attributes, and the JS/Python stuff from 
chef-funnel cleanly calls the same methods as the normal Chef DSL. There are 
definitely ways to make dialects where this is not the case, but it goes back 
to the same underlying structure issue, any such dialect would have to either 
be for novelty value or have some other reason to be Not Chef™. In short I 
think as long as it is we who ar e creating the patterns, we can ensure the 
result is not crippled and follows the same patterns and meshes with the same 
tools.

--Noah

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail