Re: Why is java considered a language for "web" or "internet" programming?
Mishagam wrote:
By the way, some interpreted/dynamically typed languages, perform
comparably well to the old, "fastest language", C. Lisp, for example.
I assume this is the sentence your comment is about?
But all scripting languages will still work with
integer as object, will be still in bytecode, and will be I assume at
the least 10 times slower, I would think more like 50 time slower.
I am very curious as to where you have this information from, please
provide some references.
But in any case, you would be right in that writing a number cruncher in
a dynamically typed language is not very smart or efficient (I would use
C. If you want real number crunching performance, such as in weather
forecasting, Fortran would be your friend). Most applications are not
number crunchers and therefore the claim is not very relevant.
I assume what you think is happening is that whenever a variable is used
the interpreter has to run through a large if-then-else statement to
decide the data type and that that is what will take time. But this is
not so, at least not for perl.
When perl stores a number in a variable it also decides the data type of
the variable and stores that information as well. So when you use a
variable in an expression, it first recognises the context as being an
numerical operation and performs a bitwise test to check the data type
of the variable. This is done by accessing a memory address, which is
cached in L1 cache). If the data type is correct for the context, the
operation proceeds as normal. If not, a conversion is performed. So the
penalty is a couple of clock cycles. This does not add up to much in a
typical application, because of how modern processors work today.
A small perl internals tip, when a numerical variable is used in a
string context and the value is converted to string, the converted
string is cached in the variable object so as to not have to perform the
conversion again later on. I don't think java or any statically typed
languages does that. This is also true for the reverse case.
You should not focus on micro-optimalisations alone. There are many
benefits and disadvantages of any language, what you need to look is the
overall performance, and you might also want to include the programmer
performance and maintenance performance into the equation.
tom