[ozim]

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.

[thatwasunusual]

As the saying goes: if you don't know if you need something or not, you probably don't need it. :)

I have been using .NET (and LINQ) for many years on a daily basis, and I've yet to run into performance problems that can't be fixed by either rewriting the LINQ statement or do some other quick workarounds.

But will I try out ZLinq? Sure, but I won't create anything that depends on it.

[Jordanpomeroy]

I think many people don’t need to worry performance of reference type allocations vs value type.

I don’t mean to assume you do or do not need to worry about that consideration. But 99% of the code I’ve written does not need to be concerned about it.

[gwbas1c]

It really depends on how simple / complex ZLinq is. Sometimes simple libraries are "done" and don't need constant updates.

[ozim]

Guy just published - definitely not finished. In 2-3 years after couple thousand people use it and bugs shake out it might be done.

[Atotalnoob]

It passes all of the tests for dotnets implementation of linq….

Seems pretty bug free for a first version.