For the 0.3 release, we want to clean up and trim down some functions that are part of the "bootstrap" process for Dojo. The full change list is on the BootstrapBloat page, but this post will specifically highlight methods that are targeted for removal. If this causes you incredible hardship, and defining a compatibility package won't help you, then please let us know as soon as possible. Targeted for removal:

• dj_debug() (use dojo.debug() instead)
• dj_unimplemented() (use dojo.unimplemented() instead)
• dj_deprecated() (use dojo.deprecated())
• dj_inherits()
• dojo.hostenv.setBaseScriptUri()
• dojo.loaded() (Alex/Dylan, can we really remove it?)
• dojo.hostenv.getLibraryScriptUri() (only keep it in hostenv_jsc.js)
• dojo.hostenv.require) (use dojo.require() instead)
• dojo.requireAfter()
• dojo.requireIf() (use dojo.requireAfterIf() instead)
• dojo.conditionalRequire()
• dojo.requireAll()
• dojo.hostenv.provide() (use dojo.provide() instead)
• dojo.exists() (change code to use dojo.evalObjPath() if possible)
• dojo.hostenv.byId(0 (use dojo.byId() instead)
• dojo.hostenv.byIdArray() (If really useful, merge the functionality into dojo.byId?)
• dojo.hostenv.conditionalLoadModule() (use dojo.kwCompoundRequire() instead). dojo.hostenv.conditionalLoadModule() will probably be kept around, but you are strongly encouraged to change to dojo.kwCompoundRequire(). The dojo codebase will be changed over to use dojo.kwCompoundRequire(). Right now dojo.kwCompoundRequire() is an alias to dojo.hostenv.conditionalLoadModule() anyway.