batman.js state of the union

An overview of the history, current state and future direction of the batman.js framework

Transcript

1. state of the union
2. A brief history of time
3. ~ 2.5 years Dec 2010 M ay 2011 Feb 2012 Oct 2012 M ay 2013 Contributors (@Shopify) Feb 2013
4. then now future
5. Ember, Angular, others didn't exist We needed a framework to build our next generation of apps on Start from scratch Huge undertaking then
6. A year to build then Shopify 2 didn't start until roughly 1 year after batman.js started A few demo and prototype apps were built while developing batman.js Early optimizations and extra features
7. A year to polish then Shopify 2 started late 2011, early 2012 First large scale batman.js app Early optimizations proved to be less useful in some cases Performance nightmares
8. Community then Good community support upfront Decent docs and APIs Sample apps Active repo & user groups
9. one more thing...
10. batman.js used to be 1 file
12. Performance then
13. but first... then
14. James' List of Major Refactors Which We Almost Certainly Will Never Have Time to Do
15. James' List of Major Refactors Which We Almost Certainly Will Never Have Time to Do 1. Batman Object'd Render Contexts 2. Bindings just tie two accessors together 3. Filtering can be done on any object, not just by Bindings 4. Different classes for fetched views & wrapper view 5. Re-write associations
16. James' List of Major Refactors Which We Almost Certainly Will Never Have Time to Do 1. Batman Object'd Render Contexts 2. Bindings just tie two accessors together 3. Filtering can be done on any object, not just by Bindings 4. Different classes for fetched views & wrapper view 5. Re-write associations APPROVED
17. Nov 2012 Full navigation of admin 93MB Paginate orders index 5 times 242MB Toggle between orders and dashboard 4 times 126MB Performance
19. Detached DOM trees
20. Nov 2012 Jan 2013 Full navigation of admin 93MB 58MB Paginate orders index 5 times 242MB 66MB Toggle between orders and dashboard 4 times 126MB 66MB Performance
22. then now future
23. Simplify APIs (mostly) Synchronous rendering No more RenderContext Batman.View refactor now
24. TestUnit inspired test suite Make it as easy as possible to test Batman apps Wraps QUnit, works well with Karma XHR and model expectations TestCase, ModelTestCase, ControllerTestCase and more Batman.TestCase now
25. Performance Nov 2012 Jan 2013 July 2013 Full navigation of admin 93MB 58MB 50MB Paginate orders index 5 times 242MB 66MB 37MB Toggle between orders and dashboard 4 times 126MB 66MB 28MB
27. now
28. Community site horribly out of date Batman is easy but no one knows Barrier of entry is artificially high Community now
29. then now future
30. Getting started guides Sample apps Community site redesign Better API docs and guides Community future
31. Improve deserialization Revisit property system Reduce object count and memory footprint Performance future
32. Model Associations Model deserialization Properties Breaking API changes Refactoring future
33. Better abstractions for common testing Improved functional testing Better view and rendering testing Testing future
34. Rails developers should immediately understand Batman Rails inspired testing Rails comparable API Rails style documentation future
35. Batman powers Shopify's Admin interface Build Batman from real life experiences and needs Build large scale JS MVC applications easily Product backed future
36. Consistent API No more breaking changes Shopify Admin backed December-ish V1.0 future
37. Shopify Admin Dashing Q, Tango planningcenteronline.com Shopify Apps, Sloth (soon to be) batman.js projects