On Friday, 19 December 2014 at 13:15:21 UTC, Mike Parker wrote:
Which obviously comes from a lack of any historical reference. If Vic had been around this community longer than he actually has, he never would have made such a remark. Walter's nickname should be Dr. No.
Well, the point is not that one should say "no", but assign priorities (and degree of certainty) to features/enhancements/fixes and attach them to milestones that gives a predictable path to a series of stable release.
So, "no" is not a good answer, but "not for release X, if this goes in it should be designed along with feature Y which is planned for release Z" is an answer that might encourage people to create a proof-of-concept-prototype without expecting it to go in right away.
