Hacker News new | past | comments | ask | show | jobs | submit login

  Put on hold as too broad by rene, davidism, vaultah, Sam, iCodez 2 hours ago

  There are either too many possible answers, or good answers 
  would be too long for this format. Please add details to 
  narrow the answer set or to isolate an issue that can be 
  answered in a few paragraphs.

  If this question can be reworded to fit the rules in the 
  help center, please edit the question or leave a comment.
Meta: It's interesting that 5 users thought that it would benefit the SO community to put this question on hold, while 100+ thought it was an interesting question. In one way, SO does keep the noise down pretty well, but this doesn't feel to me like noise. Does avoiding questions like these actually make SO a better place? Is there a reworded version of this question that would actually elicit better responses? Or is this just the joy of playing the enforcer?



I'm not a moderator, but I agree that the question is not really constructive in the scope of what stack overflow is supposed to do: answer questions to specific problems. The question itself is interesting as are the answers, and the whole discussion around it is great, but it doesn't belong on that site.

Why is python not as fast as JavaScript is a completely different question than "An internal error occurred during updating maven project". The later seeks a solution to a problem while the former only encourages discussion but is impossible to solve (because it's not a solvable question).

So, I feel this question was appropriately tagged, or perhaps even not aggressively enough.


I asked this question because I was a little bit frustrated with one page in my app which rendered in 800ms. 100ms was db time, the rest it was Ruby.

Sure, the answers won't help to solve my _specific_ problem. However in general I like to known how things work. It is not enough for me to read ordinary info about Ruby symbols. I have to read Ruby source code to understand them better (1) Thanks to this I understand Ruby symbols gc issue, a new feature of Ruby 2.2

Even more important is _intuition_ one can build reading the answers. Intuition about languages in general. I really like duck typing languages. Sometimes I need raw performance. So should I plan migration to statically typed languages (Java, Scala)? Or is it better to invest my time into learning Dart? Does Dart have _potential_ to solve my specific requirements?

As a software architect I have to predict a future a bit. And I must say that nostrademons answer helped me to learn something new today.

1) 2011 http://stackoverflow.com/a/4879142/3315


If you're going to move to a static language, I'd recommend Go over Java or Scala. Especially if you like duck typing (it has a static flavor of duck typing). I haven't used it for anything nontrivial (you can pry C from my cold, dead hands), but it looks like it solves the problems in its domain exceedingly well.

Regarding Dart: It looks nice. At work I'm forced to work in JS sometimes (I work at a game company that does contracting, and lately clients have started needing/wanting HTML5), and my opinion is that Dart looks better than it in every meaningful way. I've also begun to get the impression that Google has moved most of the V8 engineers over to Dart, but I don't have any hard evidence for this.

Honestly without knowing your problem, it's impossible to say whether or not either of these would solve it. My guess is that either of them could, as they're both languages that are orders of magnitude faster than Ruby and both seem to have large, fully featured standard libraries.


> the scope of what stack overflow is supposed to do: answer questions to specific problems

Honestly people should read the manual then. That will give you the specific answer to your question. Stackoverflow wanted to replace other message/discussion boards in regards to programming. It's veered away from that purpose and IMHO has become cumbersome to use. If you have to worry more about how you word your question than the question itself is it worth asking there?


The way I've always thought about and used StackOverflow is as a replacement for manuals, tutorials, and bug fixes—not at all a replacement for message boards or forums.


> If you have to worry more about how you word your question than the question itself is it worth asking there?

well, you are supposed to ask a question after you have researched the solution, so the extra worry wouldn't actually be relevant.


The manual answers all questions related to programming.


I think SO is starting the get the same problem that Wikipedia has been wrestling with - editor/moderator cliques. It may be a classic bureaucracy issue - on one hand they raise the quality bar by providing a higher level of consistency. On the other hand, they may drift from what might be considered reasonable from the point of view of more and more people outside the circle...


The theory of universal deletionism states that sites with extensive volunteer moderators will invariably tend towards bureaucracy and deletionism regardless of what regular users want as mods get bored and want to feel important

You should see how excited the moderators get when they decide there's a new rule against some new kind of question


SO was supposed to mitigate this effect by making people earn their mod rights. So you only get to call other people's questions off-topic if you have a track record of contributing to the site content yourself.


I would say it's the latter. A majority of questions that I've found on SO that helped me solve a problem or answer a question have been marked as non-constructive. I don't know why people would do that from a logical perspective, but I can see how having the ability to moderate discussion would make one overzealous with this sort of thing.


It's not 5 v 100, you have to be at a certain threshold of points to vote to close a question.

I don't agree with closing questions like this either, but there are rules, those rules work most of the time and the question is broad. SO is not a Quora, it's not a discussion site, even though it would be nice to use the brain trust of SO in that way.


> SO does keep the noise down pretty well

SO also keeps jQuery signals loudest.


I think that comes from the sheer number of developers who don't understand, and haven't taken the time to actually read up on, or learn JS, using jQuery to hack together a usually working solution and then asking on SO when they hit a wall.

It speaks more to the popularity of jQuery and the use of JS by those inexperienced with it than a specific signal/noise issue.




Applications are open for YC Winter 2020

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: