Stream Implementation Analysis

I am studying a responsive ecosystem, I came from the world of AngularJS, and I have no idea which flux implementation to use ...

Can someone explain which is better considering that I like the MV * angularjs (1x) structure?

I will be grateful for your attention:

  • Differences between them
  • Goals
  • Learning curve
  • Resource Sharing
  • Testability
  • Scalability
  • compliance with new standards (both from the point of view of ES6, and with the development trends of WebDevelopment)

I found a lot of resources, but I still have a lot of doubts!

Thank you in advance

+6
source share
3 answers

I use AltJS for a new project, and frankly, I like it.

2, 4 - This is pretty bizarre because of the “sharing” (if I understand correctly what you meant by that). You create "logical" and "pure (dumb)" components that can later be used many times (it makes no sense to create the same look, but with a different logic, so you just "choose a different store" for the same "pure" "component") . It can also easily track other store conditions, use several stores at once with one component thanks to AltContainer (you should definitely try AltJS with AltContainer) and use actions from one store, while another store is updated (bindListeners).

3 - On the learning curve, I would say that it is quite easy to understand the whole concept. It will literally bring you the maximum of the day to understand the whole idea. Of course, there are more complicated things here, but other libraries also have even more complex things.

5 - You can easily test actions and stores (for example, there is an example on their page) using "AltTestingUtils". You can also mix with Chai or any other claims library that you use. So it’s nice to say

6 - well also was not the idea of ​​Flux about "scalability"? If we think AltJS is probably one of the “cleanest” implementations of this, then I would say that should be good. So far, I can say that it works for me well (although it is difficult to see the future, because now it is not so much). Although there are some tools to improve performance if there are problems with scalability (for example, AltContainer really should be set to ComponentUpdate).

7 - AltJS was made to work in ES6, at least they say it (and I use it too)

While alt examples encourage ES6 and Alt was built with ES6 in mind, it is well suited to use old, old JavaScript.

I made a AltJS post some time ago in a different thread, you might find it useful

fooobar.com/questions/29601 / ...

+2
source

Existing link here - https://medium.com/social-tables-tech/we-compared-13-top-flux-implementations-you-won-t-believe-who-came-out-on-top-1063db32fe73# .l0ui3uq2z .

However, when I started to delve into Flux, I went with community ratings on Github and the number of downloads in npm. Reflux was up on both accounts. My explanation was that if the structure is popular and many people understand and use it, it should be simple. As a newbie to React and Flux, I already had a lot to learn, and I found Reflux more understandable because it took care of the many configuration needs that Flux has. However, this may or may not be desirable for the next person if you take a purist position and want to adhere to the basic flow paradigm proposed by FB. I read that Alt and Redux are closer to him, and they are also very popular at the moment.

TL; dg; Read Flux, then read at least three to four different frameworks, and then take your pick.

+3
source

I suggest you start with Flux, and this is the original implementation of Facebook’s Flux architecture, examples will help you understand it.

https://facebook.imtqy.com/flux/

Once you understand how Flux works, you will find out and decide what other implementations you want to use, such as Redux, Flummox, Alt, etc.

+2
source

All Articles