Performance even better

[dotnetwise]

Hey friend! First of all I would like to thank you for Fiber.js as it started my curiousity and I have researched how can performance be even improved.

Hence, I have created the first version of Javasript fastClass https://github.com/dotnetwise/Javascript-FastClass

I have designed it with performance first approach and it seems it paid off.

There are two main performance tests I have tweaked:
http://jsperf.com/js-inheritance-performance/25 (I have started from your performance tests in the first place and added a couple of try and error ones 👍

The biggest change to the test was to create/call more methods so the definition of the constructors themeselves woud not have such a HUGE impact, but rather creating new Classes and calling base methods would happen way more times in real life (maybe even 500 times for one single inherited-class definition.)
So all the tests are doing a fair 1000 new A, new B and new C - and calling method1 all way up.

Then I have extracted all those that were way too weak <50% slower than native/TypeScript.
http://jsperf.com/js-inheritance-performance/26
As for the record the native is just there for reference, but obviously no one wants to use it as it has major drawbacks we all know. Nobody wants to write repetitive code, beside you'd always need to know what's the base class named for.

On the other hand when using Typescript you don't really care about the output code. You just care whether it's fast or not. So we're competing against that.
However, that's still not fair for those who can't adopt Typescript just yet.

For pure-javascript (no strings attached - no develop time compilers that is) The fastest method is the new 'guy in town` to beat.
Obviously it depends on browser's implementation in the end. Some implemented Object.prototype.method faster, others slower and so on.

I have tried a couple of interesting approaches that could work or could not, depending of everyone's secnario.

However, I''ll let everyone decide for themselves what's the best adoption for them.

Bottom line, please have a look on my approaches and performance timings.
Any improvements are welcome. Besides competition in performance is always a good way of imposing new creativity, so I dare you for an even faster/better version! It's not that mine or yours is better, is that the whole world can benefit from both.

I haven't approached multiple inheritance nor mixins yet, but I might do so in the future.
I did however tackled the private methods problem and sorted it out. (see the example in the wiki pages).

With the hope this long and message won't be so borring I'm looking forward to seeing your thoughts!

Enjoy!
Laurenţiu Macovei
DotNetWise

[Iheartweb]

@dotnetwise looks pretty good.

In reality I would use inheritWith 95% of the time. I think the sugar it provides around prototypal inheratence is the best part of your library. (It's the best part of fiber too)

@krisk It looks like you have some competition. First ping pong, now this? What's wrong?

[dotnetwise]

Thanks @Iheartweb. I think all libraries are great in the real world but some of them are just considering some bad design which turns out to be after the performance tests.
Ideally we'd all learn from each-other and make them all even better.

[dotnetwise]

I have improved inheritWith so that it makes use of __proto__ which made it even faster.
Documnetation and performance tests are on the project page

Still waiting for a feedback from you!