Store: Benefit?

Created on 5 Mar 2018 · 6Comments · Source: ngxs/store

Hey!
Flying over the Code, but dont see the benefit over ngrx
If there is any could you please explain what the benefits are?

Source

ToxicToast

Most helpful comment

I'm working on a article about this but here it is in short:

Switch statements suck
Spreads in every state mutation are redundant, let the framework do it for you
Boilerplate hell ( 4 files for a single store )
String consts EVERYWHERE
Effects are difficult to understand, write and maintain
You should be able to listen for the result on dispatch
Sometimes you need DI in your 'reducers'
Its more Angular-like code style
It supports promises in addition to observables

amcdnl on 5 Mar 2018

👍6

All 6 comments

I'm working on a article about this but here it is in short:

Switch statements suck
Spreads in every state mutation are redundant, let the framework do it for you
Boilerplate hell ( 4 files for a single store )
String consts EVERYWHERE
Effects are difficult to understand, write and maintain
You should be able to listen for the result on dispatch
Sometimes you need DI in your 'reducers'
Its more Angular-like code style
It supports promises in addition to observables

amcdnl on 5 Mar 2018

👍6

Here's another perspective for @ToxicToast and others to consider:

I use, like, and teach NgRx, have been using with the Redux/Elm pattern since its emergence. I'm familiar with many of the underlying ideas from prior work under the banner of CQRS/ES. ... and am still very interested to see where ngxs ends up. I don't think it's necessary to see immediate benefits over or "vs" NgRx; rather, just notice that NgRx now has some constraints in its evolution. It has a decent and growing user base, so must evolve somewhat carefully and slowly, in a mostly backward-compatible way.

A new thing like ngxs which currently has (I would assume) zero production users, can experiment with new ideas, syntax, semantics, etc. Maybe what emerges will either make this library popular, or influence other libraries in a useful direction.

kylecordes on 5 Mar 2018

👍1

Maybe "benefits" was the wrong term that ive used since English isnt my native Language

But what @amcdnl wrote sounds pretty interesting and neat - i will use it very soon in another private project of mine

ToxicToast on 5 Mar 2018

See: https://amcdnl.gitbooks.io/ngxs/content/introduction/why.html

amcdnl on 17 Mar 2018

A new thing like ngxs which currently has (I would assume) zero production users
@amcdnl Is it safe to use it for production application?

shivamd20 on 26 Aug 2019

@shivamd20 That statement was from over a year ago, when the library was essentially 5 days old.
There are many production projects running on it now. We have over 25 000 npm downloads every week. Yes it is most definitely safe! ;-)