Different between ngneat/query and TanStack/angular-query-experimental

[clicktodev]

A detailed guide about the pros and cons of each implementation would be great.
https://github.com/TanStack/query/tree/main/packages/angular-query-experimental

[rbalet]

Hi @hichemfantar,

I was really interested in finding the answer to your question, so I did a bit of research. Please take my words with a grain of salt, as I'm not a professional in the matter.

From what I gather, even though TanStack/angular-query-experimental is labeled as experimental, it is not as experimental as it seems. The author of the extension has indicated this, but he cannot guarantee 100% that the library won't undergo changes. Therefore, he prefers to keep the experimental label for now, although it's unclear how long this will last.

Regarding ngneat/query, it was an excellent initiative by Netanel Basal. At a time when TanStack (also known as React Query) was only available for React, he transitioned this library into the Angular ecosystem.

Here’s my understanding:

NgNeat/query

Established Library: An older library that works perfectly as is and is still maintained.

TanStack/angular-query-experimental

Newer Library: A newer, still "experimental" library that is likely to be enhanced in the future.

My take

I've tried to migrate to TanStack, but I do find ngNeat/query to be easier to user, even if they are really similar.
I'm but planing to move to TanStack in the future.

My Own Question

@NetanelBasal What is your take on that? I'd be glad to hear from you! :)
(I can also delete my comment if it's completely wrong '^^).

[NetanelBasal]

My perspective is straightforward: I believe RxJS is the best approach for handling asynchronous operations. Personally, I don't use the signal API; I included it here solely due to community requests.