personally, one of the only things i feel sublime is not doing things right is with the plugin system. not that i am saying the plugins or other enhancement are not good, to the contrary, i love it, but their management is very poor.
in the past we had a discussion over it, and few of us (including me) said they use some kind of revision control for this. i feel this is not the right solution. let me describe some examples:
i use CTags plugin, how can i know if i am up to date? how can i check the latest version, but also fall back if some bug slipped in?
i wrote some snippets for erlang, will they be there (Packages/Erlang) also on the next version update? won't they be overridden? can i be sure? and if someone else just wrote snippet with the same name? and how can i even know if a new snippet with the same name exists already?
why do i need the Groovy package (no offense groovy guys) if i don't even know for what it is?
how can i distribute my snippets/plugins easily between my friends and co-workers? some of them wrote already their versions, how can they choose?
i wrote a new package, do i need to zip it and expect them to extract it on %appdata%/.../Packages? and what if they and me still keeping adding changes? how will we merge it all? if we chose to use a revision control, do i expect from each of them to (1) svn update (2) copy to %appdata%/.../Packages (3) still, what about merges? or should they svn the appdata%/.../Packages itself?
i think that if we solve those issues, we'll have a dream-machine. as jon said, sublime is going to rely on enhancements, plugins, snippets. so their management should be a breeze, easy to pick and add, easy to use. last steps on the snippets, was wonderful, lets keep it up