Yeah, the thought was for "an optional field".
I tend to downvote monks who persistently ask for new features without ever volunteering to write the code too.
I'm not good enough to write perl for this site. I'd easily volunteer to help with SQL, though.
| [reply] |
If it's optional to display, that is certainly better. I tend to downvote monks who persistently ask for new features without ever volunteering to write the code too. Heck, I guess I just like downvoting. :P Are you talking about "i need this feature" type requests, or "I think this feature has merit" type requests?
How do you know how much code is required? (a lot of the requested features already have code written for them)
| [reply] |
It's irrelevant how much code is required if asking for someone else to do it. I've read the Everything Engine code, it's a hot mess and with all respect earned by the gods and janitors for their efforts, improvements, and contributions I think it should be ditched and I have volunteered to participate as a dev more than once should that shining day come to pass.
| [reply] |
| [reply] |
"I think this feature has merit" type requests?
I like discussing things. I'm really curious to hear people's opinions here, as many of the monks here are both weathered and intelligent, though it is so often seen as a request. :(
Feature discussions are often a fun way to flesh out ideas, which itself is quite satisfying. Heh, half the fun of development is working out the idea. Design first, and they no longer want to code, because the rest boring. (At least for the MBTI's Ps, which accounts for ~50% of the population.) Others love working out ideas, and doing anything about it afterwards is a separate question.
I'm guessing talking about an idea is seen as a ruse for asking for an implementation, and therefore frowned upon. Too bad. Fleshing out an idea can interest more people to get involved in the first place, making any changes a more than one person effort.
| [reply] |
| [reply] |