I've just been using ST for a few hours but it occurs to me that some plugins (notably RubyTest) are bending over backwards to do things that maybe should be provided by the existing Build System architecture.
If Build Systems could provide more that just one "cmd" then each file type could have its own system for doing a whole panoply of common tasks:
* Build (as currently defined)
* Run (build and execute)
* Verify ("lint" for .c, "ruby -cw" for .rb, http://validator.w3.org/check for .html)
* Preview (turn the file from Markdown etc. into HTML, then launch a browser)
* Test (for foo.rb, open and run foo_test.rb)
The above is probably overspecified, but think about what it would take to have a common system at least for "Build/Run/Preview". Then every file type would have the same key command and menu option for these common tasks.
Customer support service by UserEcho