Re: Feature management
Hi Duke,
Yes, prioritizing is good - but deciding on what gets priority is an issue.
Its possible that a single vocal person's feature proposal will cause
a lot of noise on this list and hence get priority over another proposal
that has wider appeal. Also the sheer bandwidth expended on one person's
pet proposal can be significant in discouraging newbies.
With an agreed set of criteria, priority becomes transparent.
I betcha that Rob has a criteria list - even if its undocumented
and only in his mind. I'd like to see that list! We have had hints
though, and the rare emphatic "NO" from him too, eg "goto" and
certain forward variable referencing.
I dunno that Euphoria needs to be optimized for a particular purpose if
that detracts from its original purpose of being a general purpose
language. By all means add extras but be exceptionally wary of breaking
backwards compatibility. The super library you mentioned would be OK.
IMHO we have an opportunity to take a step back and say how we want
to take Euphoria forwards before we concentrate on specific features.
Kinda like writing code itself; its best to think about the goal and
strive for that - don't be tempted to add features as you are going along.
Regards
Alan
|
Not Categorized, Please Help
|
|
