Skip to main content
replaced http://cs.stackexchange.com/ with https://cs.stackexchange.com/
Source Link

No, you didn't misunderstand “not constructive”. Your problem is that a large part of the Stack Overflow community does not understand the topic of your question. This is fairly common with language design questions.

Programming language design is a science, albeit a poorly-understood one. There are reasons to make this or that choice, which can have to do with nice theoretical properties, ease of implementation, performance, etc. To complicate matters, language design is also a historical process, so sometimes the reason is “we didn't understand the implications at the time” or “the author of the spec made a typo”. Both kinds of answers call on facts and specific expertise. The former kind is considerably more interesting than the latter, but usually if the asker had known he wouldn't have needed to ask.

Programming language design is on-topic on Stack Overflow because it has a direct impact on programming. It is also on-topic on Computer ScienceComputer Science since programming language design is a branch of CS. Unlike the SO community, the CS.SE community understands CS, so I think your question would get a warm reception. However, the CS.SE community is vastly smaller than the SO community. In practical terms, you are far more likely to reach someone who knows the answer on SO than on CS.SE.

(As an advocate and moderator of CS.SE, I hope this will change. Hey, y'all programming language designers, come and join us on Computer ScienceComputer Science!)

No, you didn't misunderstand “not constructive”. Your problem is that a large part of the Stack Overflow community does not understand the topic of your question. This is fairly common with language design questions.

Programming language design is a science, albeit a poorly-understood one. There are reasons to make this or that choice, which can have to do with nice theoretical properties, ease of implementation, performance, etc. To complicate matters, language design is also a historical process, so sometimes the reason is “we didn't understand the implications at the time” or “the author of the spec made a typo”. Both kinds of answers call on facts and specific expertise. The former kind is considerably more interesting than the latter, but usually if the asker had known he wouldn't have needed to ask.

Programming language design is on-topic on Stack Overflow because it has a direct impact on programming. It is also on-topic on Computer Science since programming language design is a branch of CS. Unlike the SO community, the CS.SE community understands CS, so I think your question would get a warm reception. However, the CS.SE community is vastly smaller than the SO community. In practical terms, you are far more likely to reach someone who knows the answer on SO than on CS.SE.

(As an advocate and moderator of CS.SE, I hope this will change. Hey, y'all programming language designers, come and join us on Computer Science!)

No, you didn't misunderstand “not constructive”. Your problem is that a large part of the Stack Overflow community does not understand the topic of your question. This is fairly common with language design questions.

Programming language design is a science, albeit a poorly-understood one. There are reasons to make this or that choice, which can have to do with nice theoretical properties, ease of implementation, performance, etc. To complicate matters, language design is also a historical process, so sometimes the reason is “we didn't understand the implications at the time” or “the author of the spec made a typo”. Both kinds of answers call on facts and specific expertise. The former kind is considerably more interesting than the latter, but usually if the asker had known he wouldn't have needed to ask.

Programming language design is on-topic on Stack Overflow because it has a direct impact on programming. It is also on-topic on Computer Science since programming language design is a branch of CS. Unlike the SO community, the CS.SE community understands CS, so I think your question would get a warm reception. However, the CS.SE community is vastly smaller than the SO community. In practical terms, you are far more likely to reach someone who knows the answer on SO than on CS.SE.

(As an advocate and moderator of CS.SE, I hope this will change. Hey, y'all programming language designers, come and join us on Computer Science!)

Source Link

No, you didn't misunderstand “not constructive”. Your problem is that a large part of the Stack Overflow community does not understand the topic of your question. This is fairly common with language design questions.

Programming language design is a science, albeit a poorly-understood one. There are reasons to make this or that choice, which can have to do with nice theoretical properties, ease of implementation, performance, etc. To complicate matters, language design is also a historical process, so sometimes the reason is “we didn't understand the implications at the time” or “the author of the spec made a typo”. Both kinds of answers call on facts and specific expertise. The former kind is considerably more interesting than the latter, but usually if the asker had known he wouldn't have needed to ask.

Programming language design is on-topic on Stack Overflow because it has a direct impact on programming. It is also on-topic on Computer Science since programming language design is a branch of CS. Unlike the SO community, the CS.SE community understands CS, so I think your question would get a warm reception. However, the CS.SE community is vastly smaller than the SO community. In practical terms, you are far more likely to reach someone who knows the answer on SO than on CS.SE.

(As an advocate and moderator of CS.SE, I hope this will change. Hey, y'all programming language designers, come and join us on Computer Science!)