Echo JS 0.11.0

<~>
planttheidea 2257 days ago. link parent 1 point ▲ ▼
Fair question ... two reasons.

1) The "redux" portion of this library is actually only about 10 lines of code, namely the "composeMiddlewares" method used in dispatching, and the "dispatch" method itself (which I had to customize anyway to work with setState). The rest of the library is mainly focused on providing targeted versions of what react-redux and redux-actions provide.

2) Each of those libraries have things that aren't needed here (subscribe / unsubscribe for redux, Provider for react-redux, etc.), and so making a highly-targeted version allowed me to keep the footprint small (~3.5kB minified + gzipped instead of ~13kB with the combination of the three libraries).

Replies

kornflexx 2257 days ago. link 1 point ▲ ▼
So why put redux in the name ? How a reducer can be a reducer if he is not called on reduce callback ?(for the size issue, you can use redux as a peer dependency).

I think that "redux" name part is too much.

Your concept is really good, and your code is excellent, why not choosing your own name ?

I see that you have implemented reduxsauce api (that is cool too).

In fact the whole thing look like hyperapp actions/state API. 

I have the same frustration of writing class for my components.