Benchmarks between JS classic methods and Sanic methods here.

Another new day in the Javascript's world, and this fucking Array.prototype.map() function is always slow. But Sanic is here to save Javascript from the performance hell. GOTTA GO FAST !

sanic.js is a library which increases Javascript natives functions performance to the detriment of some unused cases of EcmaScript specification. For example, this library removes hasOwnProperty() check in Array methods, because nobody uses Array methods for an Object. (Why am I saying that : See Note 2 of this paragraph).

This project has 2 common uses :

• like any other library with a classic object with methods.
• with a special require changing prototype of natives objects concerned (Array, Object, ...) (monkey patching).

gosh you're changing prototype of native objects taht's baaaaaaaad !!!!! :((

The advantage of this bad technic is performances of all library called after sanic.js will be impacted, and using this technic is only one line away :

    require('sanic.js').changeMyWorld();

Due to the danger of the library, there's a lot of unit test and performance tests to try to protect you from bugs. But anyway, there are always bugs, so please report them in Issues section.

    npm install --save sanic.js

This mode replaces all prototypes methods by their Sanic equivalents. Sanic methods are written with same parameters than natives prototypes methods. The goal is to give faster functions without any code adaptation.

    require('sanic.js').changeMyWorld();

    const myArray = [1, 2, 3, 5, 8];

    console.log(
        // Yeah, Sanic is activated but there's no code to change
        myArray.reduce((acc, n) => acc + n)
    );

In this mode, all functions need the object to use to the first parameter and all classic parameters after.

    const Sanic = require('sanic.js').Library;
    const myArray = [1, 2, 3, 5, 8];

    console.log(
        Sanic.Array.reduce(myArray, (acc, n) => acc + n)
    );

• Array.prototype.every()
• Array.prototype.fill()
• Array.prototype.find()
• Array.prototype.filter()
• Array.prototype.forEach()
• Array.prototype.map()
• Array.prototype.reduceRight()
• Array.prototype.reverse()
• Array.prototype.some()

• Object.assign()
• Object.clone() (optional method)

    # Run all benchmarks
    npm run benchmark

    # Run specific benchmarks
    npm run benchmark Array.reduce Array.map

    # Method can be set to 'all' to test all methods of a class
    npm run benchmark Array.all

Benchmarks here

To create this library, I do some bench tests on each function detailed in EcmaScript. But sometimes, natives functions are faster. So I keep my bad functions and I call them experimental functions. That's why there are more functions available in benchmarks than in lib.

If you want to test the performance of these functions (in the case of you want to help this library or others things) :

    # Run all benchmarks
    npm run exp

    # Run specific benchmarks
    npm run exp Array.map Array.indexOf

    # Method can be set to 'all' to test all methods of a class
    npm run exp Array.all

This is the same command line than benchmarks, but it enables a new flag which allows using experimental functions.

• Array.prototype.concat()
• Array.prototype.includes()
• Array.prototype.indexOf()
• Array.prototype.join()
• Array.prototype.lastIndexOf()
• Array.prototype.push()
• Array.prototype.reduce()
• Array.prototype.shift()
• Array.prototype.unshift()

MIT (LICENSE)

• KBDev
• ProMyze