Client-side JavaScript Framework (Batman.js)

10/28/2014

This post details the decision to deprecate and replace the in-house JavaScript framework Batman.js. The primary drivers for this decision were performance issues (memory leaks, response time regressions), significant code duplication between client-side and server-side logic, and poor developer onboarding due to the framework's complexity and lack of documentation. The team opted for a new architecture involving ERB views, server-side rendering, Turbolinks, and a custom JavaScript binding system to address these challenges, aiming to improve developer productivity and reduce codebase complexity.

11/7/2011

This post details the author's positive experience using CoffeeScript for three months while working on the Batman.js framework. It provides a code example comparing JavaScript and CoffeeScript for object iteration, highlighting CoffeeScript's conciseness and reduced error potential. It also addresses debugging concerns, explaining that compiled JavaScript can be examined and optimized, and discusses the workflow integration of CoffeeScript compilation into the development process.

9/19/2011

This post introduces Batman.js, Shopify's open-source CoffeeScript framework for building single-page applications. It details the framework's core features, including a runtime layer for observing data changes and computed properties using deep keypaths, a view system that leverages direct data binding to HTML elements for efficient updates, and a model layer for data persistence. The post highlights the framework's advantages over existing solutions by focusing on developer experience, boilerplate reduction, and performance through surgical DOM manipulation.