A quick look at WireBox

G'day:
A coupla days ago I had "A quick look at DI/1", after having my interest piqued by Chris' presentation "Dependency Injection with DI/1". That went quite smoothly, so to kill some time after CFCamp, I decided to do the equivalent exercise with WireBox.

I've picked a framework. Well: you've picked it for me (UPDATED)

G'day:
Right, so it's 07:45 on Saturday, I've been up since 05:00, and I'm at LHR sitting at the gate for my fortnightly trip to Ireland to see my son. And I've got an age to wait before boarding, so I'm gonna get as much of my article written as I can on which framework you've decided I should use (based on me following the groupthink).

Firstly: thanks everyone for filling-in my frameworks survey: it got over 50 responses - and fairly quickly - which is great. I've parked it now.

Here's the analysis of the breakdown.

Oops
Thanks to Seb (in then comments) for pointing out some errors in my analysis.  It seems that in the process of transferring data from various devices and apps I'd copy and pasted some stuff incorrectly.  And I concede I did not recheck them before committing them, which is a bit of a schoolboy error.  I'm glad someone is paying attention to what I'm doing (as I'm clearly not!).

So, anyway, I'm updating the results below (and will indicate clearly where they've changed).

One thing to note... the bottom line now has me using a different framework than I had indicated I was going to yesterday...

Enough with the Surveys, Cameron! This time: frameworks

G'day
Yeah, sorry, I'm going to ask you to do yet another survey (update: I've stopped collecting results for this, and have done the analysis on it in this article).  I'll stop for a while after that.  Unless I think of something else about your practices I want to find out about, I mean ;-)

Unlike the other ones where I want to simply get a sense of the zeitgeist (and perhaps get it onto Adobe's radar), this one is to help me out with my dev work.