Developers often get excited about the Robotlegs filesize footprint—adding less than 20k to your published swf. We’re much more excited about the Robotlegs cognitive footprint—how little there is to learn to get up and running with Robotlegs.

Robotlegs was always intended to be a pareto^[1] solution: it’s the 20% of functionality that solves 80% of your programming problems. The YAGNIator (YAGNI = you aren’t gonna need it!) was applied ruthlessly. This means that you can carry it in your brain’s pocket: complete use of the core Robotlegs framework only requires you to understand how to use eight classes. Yes, eight. That’s all. And these aren’t monolithic enormous classes. Most Robotlegs apps require you to make use of less than twenty methods within the framework. And Robotlegs incorporates only two custom metadata tags and, in practice, most applications only ever require the use of the [Inject] tag. More on those metadata tags later.