As you mention, the questions that work on Stack Exchange are ones that have a specific, singular, and solvable problem: that is, you ask a question, you get targeted answers that may or may not help you solve the problem. If they don't, you edit your question to clarify. If the answers are unclear, you ask the answerers to expand on their answer.
In this case, that's not what happened: you've presented a position, asked several questions, and attempted to carry on a conversation with all the answerers in a now deleted answer complete with your own thoughts and ideas about the subject. That's not really what Stack Exchange is about: we're not a discussion board where free-form conversations can take place about a general topic.
The blog post Real Questions Have Answers talks about this type of problem and provides specific guidance that is codified in our FAQ (emphasis mine):
What kind of questions should I not ask here?
You should only ask practical, answerable questions based on actual problems that you face. Chatty, open-ended questions diminish the usefulness of our site and push other questions off the front page. To prevent your question from being flagged and possibly removed, avoid asking subjective questions where …
- every answer is equally valid: “What’s your favorite ______?”
- your answer is provided along with the question, and you expect more answers: “I use ______ for ______, what do you use?”
- there is no actual problem to be solved: “I’m curious if other people feel like I do.”
- we are being asked an open-ended, hypothetical question: “What if ______ happened?”
- it is a rant disguised as a question: “______ sucks, am I right?”
If your motivation for asking the question is “I would like to participate in a discussion about ______”, then you should not be asking here. If your motivation is “I would like others to explain ______ to me”, then you are probably OK.
So if you distilled all the discussion you were trying to have in all the comments, and all the opinions you might have about a topic, what is the exact nature of the problem you're trying to solve? Asking about that likely is going to be a good fit for us.
Try to ask yourself, "what does a correct answer to this question look like?" If it's hard to imagine it, the question is likely a discussion topic, and should be revised. That is, if you're not getting the answers you want, your first inclination should be to tighten up the question, not to initiate a discussion about your opinions or thoughts about the topic.
To speak to the specific nature of this question, you wanting to know what language you should switch to, that's off-topic here unless it's particularly specific. That is, you have a specific use-case and you need to know if a specific language would be more appropriate: perhaps something like, "Can I interact with an RDBMS using something other than SQL?" or "How can I develop iOS applications without knowing Objective-C?"
For more information about why the more general "What language should I use?" is off-topic, check out the question, Why is “what language should I learn” considered off-topic?:
The simple answer is that the question as stated "which language should I learn next?" is unanswerable.
The only answer anyone should give is always "it depends" - which isn't an answer at all.
Ultimately it's not a real problem. The next language you should learn is largely determined by the project you are working on and unless you are in the rare situation of having complete freedom over what you do this will have been chosen by someone else.
As to other questions, feel free to flag questions you don't believe fit these criteria for moderator review. With over 12,000 questions asked, some slip through the cracks of community moderation.
