Monthly Archives: July 2014

Announcing a v8-Natives v0.0.1

What are v8-natives, you might ask?    

Well, they are the mostly undocumented javascript commands that control the v8 engine in Google Chrome, Opera and Joyent Node.js.      Some of the commands are %CollectGarbage(), %GetV8Version(), %GetOptimizationStatus() which ties with my other favorite of %OptimizeFunctionOnNextCall()


What can I do with them?

You can tell the engine to Optimize a routine, un-optimize a routine, never optimize a routine, ask it about internal data structures of an variable/object, and one of the most important items is ask if a routine is optimizable.


Why is this important?

Well, the v8 engine has several compilers built in; the lowest compiler is just a full featured javascript interpreter -- it is fast; but compared to one of the actual compilers it is so slow that molasses moves faster.     Do you want to figure out which of your code can be promoted to the faster compilers?   Do you want to see what code is a bottleneck even though at a glance it actually looks good?


So, which of these routines optimizable?

function sum1(a,b) {
try {
var c=a+b;
} catch (err) {
return -1;
return (c);

function sum2(a,b) {
return, arguments);

function sum3(a,b) {  return  sum(arguments);


Look no further:

Available on isle 15, at the deep discount of totally free; we now have all the tools you need to answer the above questions.    A fully working support library that wraps over 20 of the internal v8 native commands in a simple to use library that will not crash your script no matter if you have the v8 native support turned on or off.  Can be left in your app and deployed; and finally   supports both Node and Browsers.

Simple things like "v8.helpers.testOptimization(sum1);"  would tell you right away if the sum1 can be optimized....   Or v8.collectGarbage() will do a full GC before you run some timings on a performance critical code...   Lots of things to help your inner-performance surface.

You can get it at your local npm repository:  npm install v8-natives or check out the github page @



fluentReports v0.0.6 Release

We are happy to publish the latest version of fluentReports.

Major Features:

This version brings fluentReports back up to working with the latest and current version of pdfKit.   It also maintains backwards compatiblity with the older pdfKit versions.   As I move forward this compatibility maybe removed unless you let me know on the page why you believe I should maintain compatibility.

This not only retains the compatibility with buffer, and write file and now adds the pipe support.     It has not been tested; but I believe fluentReports should work client side as the only code that would be "broken" is the "write to server file" type and you can't use that client side anyways.  If you test it client side and it doesn't work; let me know in the issues.

Minor Bugs Squashed:

  • Count could throw an error in the paged support.
  • Added outputType (supports buffer, pipe, and defaults to file)