Echo JS 0.11.0

I'm not sure how/why this is significantly better than current tools around applications and state management.  Is this really better than Inferno+MobX, or any other react-like JSX supporting engine and a flexible state machine for that matter?

I'm also not seeing how this approach is any more OOP than so many other frameworks I've seen in the past 5 years.  I'm not even talking about framework fatigue, I'm talking about not being sold on why this is any better, let alone why there are more upvotes than the vast majority of posts from this site.

Thanks for your reply. 

1. I don't know much about Inferno, but AFAIK it has, together with other react-like engines, about 50-80K of mini-gz-size. My framework is minimal and small, 2.6K. In my opinion it is not "better", but another way of developments.

2. I didn't have a goal to make something "more OOP" then anything else. My idea was to implement my understanding of OOP, modularity and invariant development. It is achieved by implementing of system of Actions/SubActions. Each class of SubActions doesn't need to know anything about global state and particular states that other SubActions classes control. Unfortunately I had no time to explain it in more details in some documentation, I'm sorry.

3. My friends who know and understand my ideas behind HyperOOP and Faqtor, voted for my post.

2. Gotcha... there's just so many new takes on this, with what at a glance are very minimal changes to existing options it's hard to gauge.

3. Very cool that you've been able to get that level of involvement.  I tend to be skeptical when I see that many upvotes and no comments, and only a very thin readme.

1. out of order on this.  It would be a good idea to spell out some of the differences like that.  Inferno[1], iirc is a about 8k min+gz, it's also one of the fastest frameworks out there for react-like use.  MobX[2] is a pretty decent state machine built around E6X proxies and is a pattern not too dissimilar from your own.  I'm more of a Redux fan, but can see the appeal.

I didn't mean to come off as a condescending ass.  I just see so many me too frameworks that support JSX and minimal state machines that don't really provide much over what's out there and relatively popular already.

Overall, would just suggest expanding the README.md to include a bit more on the reasoning, and a multi-layer example in addition to the minimal one and maybe a canonical todo-mvc[3] example and an implementation of the benchmarks inferno.js[4] covers.

[1] https://www.infernojs.org/
[2] https://mobx.js.org/
[3] http://todomvc.com/
[4] https://www.infernojs.org/benchmarks

Also our site [1] can be considered as multi-layer example [2].

[1] https://hyperoop.github.io
[2] https://github.com/HyperOOP/hyperoop-site

I expanded Readme [1] following your advice.

But I cannot open the page with inferno benchmarks.

Note that HyperOOP together with Inferno both included in krausest benchmarks [2]

[1] https://github.com/HyperOOP/hyperoop/blob/master/README.md
[2] https://github.com/krausest/js-framework-benchmark

Isn't my Todo enough (https://codepen.io/algebrain/pen/GwZWLg)?

Thanks for your advices.