In the article author writes about linq.js that he is not maintaining anymore but someone forked it.
I guess this library will at some point end up unmaintained after author is bored with it.
So I would not use it in any of my production code of a web app unless I get some problem I need to fix with this library specifically. Replacing all just because “it is faster” doesn’t seem good enough.
I guess this library will at some point end up unmaintained after author is bored with it.
So I would not use it in any of my production code of a web app unless I get some problem I need to fix with this library specifically. Replacing all just because “it is faster” doesn’t seem good enough.