I think the demos are intended to show how you can use robotlegs in a particular way to achieve a certain result.
As in any programming language I've ever looked at, the illustrations often use a fairly simple use case (to make it easy to understand and save cognitive space on the problem) and thus the solution can seem overly complex because the objective isn't to solve the problem, the objective is to solve the problem using a particular functionality that you want to demo.
The reasons for using a framework go well beyond solving the problem in front of you. We might choose to use the robotlegs framework to allow for growth, to make it less painful when unanticipated complexity emerges, to create a greater uniformity across all our projects so that we can easily read our own (and other's) work in the future, to create greater discipline about employing tried and tested patterns ... etc.
With a very simple problem, the 'simplest' solution is often a short functional programme - forgetting callbacks, listeners, patterns... hell, object-oriented is often over the top for a really simple problem. We could go back to as1 and stick some functions in the timeline and be done with it!
Support Staff5 Posted by Shaun Smith on 16 Jul, 2010 02:13 PM
The Cafe Townsend demo was contributed by a Robotlegs user, and
I believe he was trying out various modular techniques - I haven't
actually looked through all the code, so I can't comment as to it's
complexity, or applicability to general app dev.
Have you looked through the other demos in the bundle?