Thanks for your point, and honesty. Appreciated, as I have had a few blanks. Any help in making it simpler to understand would be appreciated!
Are you familiar with the benefits of RequireJS in not needing a build during development to load say CoffeeScript or LESS? Then we run a build and get all these things inlined and compiled thanks to dependency tracing.
ZestJS takes this a step further and loads an entire widget (say a popup or image gallery) - template, CoffeeScript and LESS with a single require on the client for rendering dynamically, without needing any build... the resources are compiled in the browser. Then we can run a normal RequireJS build with dependency tracing and render that same widget on the client with our resources built and compiled.
It's a few steps to grasp at once, but with RequireJS experience it would be a little clearer I think.