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.
So, I feel this question was appropriately tagged, or perhaps even not aggressively enough.
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
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.
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?
well, you are supposed to ask a question after you have researched the solution, so the extra worry wouldn't actually be relevant.
You should see how excited the moderators get when they decide there's a new rule against some new kind of 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 also keeps jQuery signals loudest.
It speaks more to the popularity of jQuery and the use of JS by those inexperienced with it than a specific signal/noise issue.