Hi,
My understanding of this optimization in V8 is that it's laser-
targeted
at probably the biggest bottleneck of Javascript: property lookup.
Excuse my curiosity, but my basic understanding of this optimization
is like this: in JS, you don't have classes, so every object is
On Sep 4, 2008, at 12:29 AM, Charles Oliver Nutter wrote:
Attila Szegedi wrote:
So, on the first sight, it appears to me that TraceMonkey's type
specialization is the one feature from these three new JS engines
that
would make sense in JVM dynamic language runtimes.
I've toyed with
On 9/4/08, Martin Probst [EMAIL PROTECTED] wrote:
Hi,
My understanding of this optimization in V8 is that it's laser-
targeted
at probably the biggest bottleneck of Javascript: property lookup.
Excuse my curiosity, but my basic understanding of this optimization
is like this:
On Sep 4, 2008, at 1:05 PM, John Wilson wrote:
The fact that Javascript does not support threads considerably
simplifies the situation.
Well, JS as such has no threading or other concurrency primitives,
this much is true. But you can have a JS environment where a program
accesses objects
On Sep 3, 2008, at 11:56 PM, John Rose wrote:
On Sep 3, 2008, at 2:23 PM, Attila Szegedi wrote:
Well, we certainly live in interesting times, at least as far as
JavaScript runtimes go...
To paraphrase a loan commercial: When VMs compete, language
implementors win.
TraceMonkey's type
On 9/4/08, Martin Probst [EMAIL PROTECTED] wrote:
Hi,
My understanding of this optimization in V8 is that it's laser-
targeted
at probably the biggest bottleneck of Javascript: property lookup.
Excuse my curiosity, but my basic understanding of this optimization
is like this:
Martin Probst wrote:
Now when you have a class based language like Python or Ruby, you
already have these sets of similar things where the same property
names resolve to the same things (the classes). I.e. if your foo.bar
statements gets hit with foo being a specific instance, you can
