mattkrick/meatier

who is optimistic, it sends a doc back to the client where it is compared to the original action. If the doc matches, the optimistic change is reverted & the persisted change is applied. When you close the kanban app, the subscriptions are unsubscribed and the reducers are removed from the store. If you open it again, it will show you the latest data, but no changes will be made until you make one. The whole thing is an experiment to see if we can get Meteor-like functionality without the monolithic structure. If you're a fan of Meteor, this project isn't for you. If you're a fan of experimenting with new technologies, welcome! ##How it doesn't work - You have to specify the database schema (but it's worth it) - You have to write your own validations (but it's worth it) - You have to write your own mutations (but it's worth it) - You have to write your own subscriptions (but it's worth it) - You have to manage your own reactivity (but it's worth it) - You have to use a different build system (but it's worth it) - You have to manage your own packages (but it's worth it) - You have to specify the server location (but