For those of you living on the bleeding edge, I discovered a document describing features recently added to amaroK "Fast Forward" 1.4 in SVN. Although this document is a work in progress, it should give you a good idea of what to expect in the next major amaroK release.
It's great that we can now hide browsers we don't use. All I really want is the context browser, plus a file browser which starts in my music directory. Using it like this just crashed on me, but I'm sure you guys will work that stuff out soon enough :)
BUT... does it just hide those browsers? Would it be possible to reduce startup time and memory footprint by not loading disabled browsers at all?
Unfortunately not really, I tried to make that sort of thing possible once but too many bits of amaroK expect the browser instances to be instantiated. Unforunately amaroK will never be really lean on memory use. Not that getting rid of the browsers would help that much.