There IS a "way to say with certainty what the interpreter will do". You just haven't taken the few minutes required to find out how!

And I figured, dumb guy. But the fact that I have determined how to overcome this defect of the language does not make this anomalous behavior becomes "acceptable" as you seem to think. Fixable or not is still a behavior that the Javascript should not have.

You're dumber than I thought. If you were better at interpreting text and had dealt more with the case described, you would have understood what I mean by random is that there is no way to say with certainty what the interpreter will do since there's no telling for sure if he will treat the "+" operator as a sum of integers or a concatenation of strings. It's happened to me more than once, I thought I made it clear to the interpreter that a variable would be a string (for example: var some_variable = "1") and later I found out he decided to treat the variable as a integer anyway, and the only solution was to force the variable as string immediately before the desired operation using a ugly hack. while in Java if you use the "+" operator between a string and an integer you will always have a string as a result, regardless of the variables positions or operations that have been made with them previously.

Oh, sorry? The language behaves in a non-deterministic way and this is my fault? From what basement you are, clueless guy?

Is because JavaScript seems to randomly decide whether it will return a "11" or "2", while in a strong-typed language the result is deterministic. On Java you knows that "A" is a string and "B" is a integer, so A + B will always returns a string "11". Whereas Javascript are not sure about the types used in A and B, so therefore is no way to be sure about what he is going to return.

I usually have a worse problem, which is when Javascript arbitrarily decides that my string variable is an integer or vice-versa. You create a string, but then you discovers - when trying to use a string function like split() - that Javascript decided to treat your string as a integer, making the split() fails without error messages.

The difference is that the "+" operator in a strong-typed language works without causing nasty surprises for you.

Because variants are useful when you want to (or most common, you need to) make a generic function to handle some information where you have no way of knowing if the input parameter will be a string, integer, long, etc. Of course it is slower than dealing with a defined type, but is usually more convenient than trying to create a separate function for each possible entry type.

Is the same shit here in Brazil. 60% tax in all international purchases made by individuals under the guise of "protecting" a nonexistent national industry (nobody makes Intel i7 in Brazil as far as I know).

As long as is optional, is interesting to have it considering that the driver will not always be able to call for help in an emergency (And from the standpoint of first responders is also interesting that a car can automatically call for help when involved in an accident).

Here we use PostgreSQL in most applications of the government, and it works pretty well.

Try to visit the recent XKCD here, as example: http://xkcd.com/1416/

On Chrome is usable, on Firefox the entire system almost freeze (using Linux Mint on a AMD Athlon II X2 250).

Sorry, only your impression. When I use Firefox on a weaker computer, the speed difference compared to Chrome is obvious. The detail is that a current machine is usually fast enough to hide this difference (but it still exists).

You completely ignored the crux of the problem: For the small inventor file lawsuits against patent infringement, he must pay. And need to pay a lot, probably more than he will see in life being a small inventor.