Hi,
The Chef engine needs to be revisited. The goal of this new version was to generalize the logic, and that is a good thing. However, the problem is that it does it at the expense of understandability by relying on string concatenation and perform:. We need to iterate on this one and look for another design, while preserving the current behavior. Would anyone be interested to dive in this area? Cheers, Doru -- www.tudorgirba.com www.feenk.com "Speaking louder won't make the point worthier." _______________________________________________ Moose-dev mailing list [hidden email] https://www.list.inf.unibe.ch/listinfo/moose-dev |
On Sun, Jul 3, 2016 at 9:53 AM, Tudor Girba <[hidden email]> wrote:
> Hi, > > The Chef engine needs to be revisited. The goal of this new version was to generalize the logic, and that is a good thing. However, the problem is that it does it at the expense of understandability by relying on string concatenation and perform:. > > We need to iterate on this one and look for another design, while preserving the current behavior. > > Would anyone be interested to dive in this area? What is Chef ? something to do queries apparently, but not very clear for me. -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/ _______________________________________________ Moose-dev mailing list [hidden email] https://www.list.inf.unibe.ch/listinfo/moose-dev |
In reply to this post by Tudor Girba-2
Isn't MooseChef destined to disappear because now we'll have MooseQuery in Moose 6.0 (haven't checked it yet, just know that it provides similar functionality and is more generic in terms of knowledge of the underlying model).
On Sun, Jul 3, 2016 at 10:53 AM, Tudor Girba <[hidden email]> wrote: Hi, _______________________________________________ Moose-dev mailing list [hidden email] https://www.list.inf.unibe.ch/listinfo/moose-dev |
I meant the new implementation provided by MooseQuery.
Doru > On Jul 4, 2016, at 11:29 AM, Usman Bhatti <[hidden email]> wrote: > > Isn't MooseChef destined to disappear because now we'll have MooseQuery in Moose 6.0 (haven't checked it yet, just know that it provides similar functionality and is more generic in terms of knowledge of the underlying model). > > > On Sun, Jul 3, 2016 at 10:53 AM, Tudor Girba <[hidden email]> wrote: > Hi, > > The Chef engine needs to be revisited. The goal of this new version was to generalize the logic, and that is a good thing. However, the problem is that it does it at the expense of understandability by relying on string concatenation and perform:. > > We need to iterate on this one and look for another design, while preserving the current behavior. > > Would anyone be interested to dive in this area? > > Cheers, > Doru > > -- > www.tudorgirba.com > www.feenk.com > > "Speaking louder won't make the point worthier." > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.list.inf.unibe.ch/listinfo/moose-dev > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.tudorgirba.com www.feenk.com "Beauty is where we see it." _______________________________________________ Moose-dev mailing list [hidden email] https://www.list.inf.unibe.ch/listinfo/moose-dev |
Free forum by Nabble | Edit this page |