One of my questions is up for closing because (I assume) it is somewhat broad and there is not one unambiguously correct solution.
I'd like to discuss this as based on the upvotes there is clearly some disagreement about whether or not this is a good question.
I would argue that the question should remain open because there are a number of questions in a similar vein (asking for peoples thoughts on different approaches, asking for best practices around a language feature, asking for possible drawbacks to a certain approach) that had great answers that clearly add to the value of SFSE.
A great answer to my question would be something like:
I've implemented something similar with dynamic components before and it worked fairly well and was maintainable as I needed to extend/refactor the input form. You can do this with something like the following:
$some sample vf and apex
Make sure to to do $foo so you don't hit $weird_dynamic_component_limitation down the line.
Even an answer that says:
I tried to implement this with a similar approach and ran into issues: x,y,z. I think you would be better off sticking with dynamic vf bindings.
would be useful to me or someone coming along later who is considering the same question.
I actually didn't vote to close your question. I added that comment because the question had "best practices" in it and based on the previous discussion on meta I thought it would get closed, but thought that it had value.
I'm generally OK with those types of design questions and learn from them. I think that whether or not they are interpreted as questions that are soliciting discussions with no real answer has to do with how the questions are asked and/or certain words in them. I have no problem whatsoever with long questions and long answers, advantages/disadvantages to X vs. Y, etc.
Some are more clear cut then others as being acceptable (e.g., which of these 2 options is more efficient), but I am in favor of erring on the side of being inclusive.
