I have this friend who might be most accurately described as a web developer. When DTrace was able to observe php he was interested. Me: “I should give you a demo some time.” Him: “Absolutely…”
When DTrace ticked Ruby off its list, he was more enthusiastic. Him: “Cool! I loves me the Ruby!” Me: “Let me know when you want that demo”.
The other day I got an IM from my friend. Him: “DTrace for JavaScript, eh?” Me: “How ’bout that, huh?” Him: “So when can I get that demo?”
Last week Brendan Gregg released Helper Monkey — a DTrace-enabled version of Mozilla’s Spider Monkey JavaScript engine. Why was this the tipping point for my friend the web developer? Probably not because he’s more fond of JavaScript than php or Ruby; much more likely, it’s because JavaScript is an observability atrocity. Even if you don’t use any probes in DTrace other than the ones associated with JavaScript, Helper Monkey is a galactic improvement on the state of JavaScript development. Consider the next 40,000 – 200,000 DTrace probes gravy.
Technorati Tags: DTrace JavaScript
2 Responses
With any luck, Apple will follow suit with WebKit if they haven’t already. The performance of JavaScript is not exactly worth showcasing in Safari.
Freddie,
At the WWDC we were certainly trying to make that point to the Apple folks. In addition to WebKit, we were hoping they’d use their inclusion of Ruby on Rails as an opportunity to use the DTrace support for Ruby.