A couple of days ago the DrProject team sent mail asking about how to optimize their use of Dojo, and luckily the solution was easily at hand. By using the build system the DrProject team was able to speed up their load times by 300% and drop the number of requests from 35 to 4.
We think one of the most powerful things Dojo can do is to give you all the tools that those of use building the toolkit use to improve our own apps. It gets to the very heart of our "build with, not on" philosophy. Dojo gives you a set of integrated tools that anticipate your future needs and the ability to quickly construct custom solutions with Dojo's rich set of building blocks. Sure, you could go with server-specific solutions or even use pre-rolled tools to improve the performance, but at the end of the day the tools that make you most successful are the ones that can be maintained by you, in your project, without requiring that you change the way you develop.

Can we see the e-mail itself?
I've been playing with dojo build system over the last couple of days, and I'd be very curious to see the raw text of your e-mail, Alex, if possible. The build system has worked nicely for me, but I would still love to do things like have it also consolidate my remaining JavaScript code that hasn't been nicely "dojoized" -- I'd like that to be folded into one file and also minified.
I love Dojo, by the way. It took me awhile to get on board because the documentation tripped me up once upon a time (years ago now), but it's become one of a handful of great examples in my mind of truly healthy open source projects that are unbelievably useful. The only one that competes with it for my line of work is Apache's MINA, but Dojo's more useful to a broad audience.
http://www.littleshoot.org
Open Source, Open Standards, Open Data
send me mail and I'll see what I can do
alex at dojotoolkit dot org
Regards
As a live
As a live example:
http://dojotoolkit.org/~dante/surveyDemo/orig.html
~150k across 72 requests
after build:
http://dojotoolkit.org/~dante/surveyDemo/survey.html
~60k across 5 requests, three being caused by using dojox.charting (dojox.gfx), which requires the additional
requests because it uses different renderer's for different browsers, so you can't effeciently roll them into a layer like you can anything else.