Hi Sergey,
On 07/15/2011 11:30 PM, Sergey Beryozkin wrote:
> Now, what I'd like to propose is to have an over-arching requirement: all the current and next proposals have to pass a
> litmus test:
>
> - Is satisfying a given requirement with a given proposal going to help users write *practical*, *real-world* code which
> will be realistically used. If it's going to be of academic interests then it has to be dropped. Otherwise API will be
> 'diluted'.
>
> Well, I guess, it's tricky to envisage all the real-world cases users will want to address with this API. But we should
> be realistic IMHO
What is your suggestion on how to measure or evaluate proposals against this requirement?
Marek