deluge initializes all plugins on startup, but initializing and loading are different things. basically, initializing means making the core aware that the plugin is there. nothing other than the name of the plugin and its location gets loaded into memory at that point (or ever, unless the plugin is enabled by the user). hope that clears things upUx64 wrote:That's already possible.johnnyg wrote:you could always give users the option to enable/disable the search bar & anonymous browser in the configuration wizard.(0.5.8)
I think you kind of missed the point. It's different thing to have small install and download package than have program with small memory footprint. And after all when I start deluge it seems to initialize all plugins even if those aren't enabled. I didn't do any in depth analysis about that. But markybob says that it won't use any more memory. That's just great.
But it would be more reassuring if it wouldn't even initialize / load modules that aren't loaded. Then it would be clear that those aren't being used. (I know, once again totally technical babble about some minor issue)
After all I don't care personally about download size or RAM usage or even CPU usage, because I got plenty of everything. Often the most expensive resource is programming resources. That's why I didn't like browser etc. Because it takes resources away from more important things (my point of view). But we all are (hopefully) allowed to have own opinions. And actually most of us (like I) don't have any authority about this, so feel free to ignore my boring long posts.
I agree about this. But when I do it, I usually seem to upset developers. Maybe my style is completely wrong. I have been doing this for 20 years now, working in software development companies.sluthead wrote: Or we can just discuss things as a community and throw ideas into the pot about it's future direction and try to do the best for the software instead of having a load of other "new" ones.
But when we're talking about programs. It seems that I often take too technical view. And forget that program is developers baby. Any criticism is a bad bad attack against his or hers beloved. And it's quite rare that someone instantly admits that something is wrong. Change might be long process and come out after a years.
AFAIK: Anyway it's important to allow throwing in ideas. And not to take any criticism personally. It's just discussion how things might could have been done. Open discussion about problematic issues is what I have been missing in many projects. Usually some easy kludge solution is taken, without even thinking what kind of problems it might cause in future. And I have seen this way too many times.
I wonder why you did read old software project managers feelings this far.

as far as the rest goes, i've been known to be short-tempered. deluge is a hobby...i dont get paid to work on it. it's merely something i enjoy doing and i like giving back to the community. with that said, since it is a hobby and for fun and i get nothing for it, it sometimes gets very frustrating when people seem to whine and try to make demands. most of the time i brush it off, but every now and then i lash out in response, even at those who dont deserve it and didnt mean any harm but were simply giving honest suggestions. i dont mean to suggest that i see every user complaint as "whining". not at all; there are totally valid complaints, and i try to take those into consideration. to sum it all up, i'm not perfect, and deluge never will be, either
