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."
On Sun, Jul 3, 2016 at 9:53 AM, Tudor Girba tudor@tudorgirba.com 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.
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 tudor@tudorgirba.com 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 Moose-dev@list.inf.unibe.ch 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 usman.bhatti@gmail.com 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 tudor@tudorgirba.com 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 Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev
Moose-dev mailing list Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev
-- www.tudorgirba.com www.feenk.com
"Beauty is where we see it."
-
Serge Stinckwich -
Tudor Girba -
Usman Bhatti