show why handlebars tends to lead to undebuggable mess with concrete examples
JavaScript Handlebars
Latest commit a779835 Mar 2, 2015 Bryce Fisher-Fleig (feat) burnIt footer now working!
Permalink
Failed to load latest commit information.
components (feat) burnIt footer now working! Mar 2, 2015
views (feat) burnIt footer now working! Mar 2, 2015
.gitignore
README.md (doc) more nits grammatical and formatting Mar 2, 2015
helpers.js initial commit Mar 2, 2015
package.json initial commit Mar 2, 2015
server.js initial commit Mar 2, 2015
users.js initial commit Mar 2, 2015

README.md

HBS-Research

Objective: Show why handlebars tends to lead to undebuggable mess with concrete examples. I've intentionally done almost everything as poorly as I can because:

  • It's incredibly addictive once you get started
  • I didn't have time to make it much worse while keeping it readable
  • Like a real software project, I did this without an upfront plan and in multiple passes

Installation

Requires npm/nodejs already be installed. Built using nodejs 0.10.x.

git clone git@github.com:brycefisher/hbs-research.git
cd hbs-research
npm install
npm start

Usage

Navigate to http://localhost:3000/ and starting clicking around. There's at least two major bugs you'll encounter as you do.

But...Why Would You Do This?

Read along with the forthcoming blog post that inspired this software project at bryce.fisher-fleig.org to learn more about some of ways I've intentionally done this badly and (hopefully) some valuable takeaways for using Handlebars in a maintainable way.