Enabling/Disabling options, keywords, libraries
CChris wrote:
>
> But it is an obvious truth, given the strong feelings that run across the
> users
> of this list, that having a configurable Euphoria would make them feel safer,
> rejecting any code that doesn't correspond to their liking, and being sure
> that
> they don't get any speed-down due to a feature they didn"t want in the first
> place.
>
Strong feels are free to run across the list but when the community makes a
decision, it's done. The instant we start enabling and disabling keywords,
features, etc... in Euphoria is the day it will die. The devs listen to the
masses w/common sense. We do not and should not listen to everyone and make
Euphoria such a mess that anyone can have whatever they want.
I sympathize with people in this area but it must be maintained. If the masses
agree and something is implemented, everyone who disagrees has two options... 1.
Live with it, 2. Go somewhere else.
I have made proposals that have been rejected by the masses. I am not going to
code it anyway and then provide a switch in Euphoria to turn it on or off.
--
Jeremy Cowgar
http://jeremy.cowgar.com
|
Not Categorized, Please Help
|
|
