This, is boomerang

    chrome.loadTimes().{requestTime, startLoadTime, commitLoadTime, finishDocumentLoadTime, finishLoadTime, firstPaintTime, firstPaintAfterLoadTime, navigationType, wasFetchedViaSpdy}
    chrome.csi().{startE, onloadT, pageT, tran}

Re: This, is boomerang

#6

Post by aristus » Thu, Jul 22, 2010, 5:02 PM UTC

Sephr wrote: post #5

Why not integrate Google Chrome's API with boomerang? The following functions are available to web content: chrome.loadTimes().{requestTime, startLoadTime, commitLoadTime, finishDocumentLoadTime, finishLoadTime, firstPaintTime, firstPaintAfterLoadTime, navigationType, wasFetchedViaSpdy} chrome.csi().{startE, onloadT, pageT, tran}

That's a good idea. There is also the WebTiming spec, coming soon to a browser near you. It's on GitHub, so....

Re: This, is boomerang

#7

Post by anin_teger » Thu, Jul 22, 2010, 5:03 PM UTC

There's another interesting project out there called the Boomerang Decompiler..

Re: This, is boomerang

#8

Post by thu » Thu, Jul 22, 2010, 5:39 PM UTC

anin_teger wrote: post #7

There's another interesting project out there called the Boomerang Decompiler..

And a bidirectional programming language: http://www.seas.upenn.edu/~harmony/

Re: This, is boomerang

#9

Post by apu » Thu, Jul 22, 2010, 6:01 PM UTC

joblessjunkie wrote: post #4

This, is a superfluous comma

Perhaps they were going for James Earl Jones' "This...is CNN"-style emphasis.

Re: This, is boomerang

#10

Post by geuis » Thu, Jul 22, 2010, 6:18 PM UTC

Sephr wrote: post #5

Why not integrate Google Chrome's API with boomerang? The following functions are available to web content: chrome.loadTimes().{requestTime, startLoadTime, commitLoadTime, finishDocumentLoadTime, finishLoadTime, firstPaintTime, firstPaintAfterLoadTime, navigationType, wasFetchedViaSpdy} chrome.csi().{startE, onloadT, pageT, tran}

This isn't meant to be a browser plugin. Reading through the docs, it seems this is meant to be a tool to measure actual performance of your site in actual user's browsers.