FUTURE.md

[f]

Hey @darcyadams, I just started creating a file called FUTURE.md. Can you inspect it and give your opinions?

Thanks! :)

[darcyadams]

Looks good to me. It's mostly ES6 stuff, which doesn't really interest me that much. As long as it's using polyfills to be backwards compatible, I say go for it.
Personally, I'm more interested in figuring out how to make a flux implementation with a developer friendly API, which will scale indefinitely. By scale, I mean function in a single page application with hundreds of components and datatypes.
Currently, the flux implementations out there seem clunky to me. There are no tools for managing your data within stores (something scheme is supposed to address) and the various APIs for components to inject actions in to the flow all seem messy and cumbersome. eg What is the point of calling and action method that just in turn calls a dispatcher method. viewTriggers is an attempt to address that issue.
As you have probably already figured out, I am completely biased towards React and think that is where the focus should be. I'm okay with leaving the door open for use with other tools, but we should not be afraid to put in React specific features, as that is where I believe the vast majority of use will be.
Overall, I'm pretty happy with where delorean is at the moment. I am using it for a young commercial project, which is going to get very large very quickly, so we will see how it holds up. Hopefully some good enhancements and optimizations will fall out of that work. Finally, I think more test coverage is needed.

[darkyen]

Any estimate on when the future.md will be done ?

[darkyen]

I'd like to contribute, actually transforming the source to multiple files and following ES 6 in them all and using es6ify sounds apt to me, What do you guys think ? We can actually distrib the library itself with es5ified version of it. and delorean.es6.js for pure es6 clients 🎯