(Fubar 3.0 is using 154kbyte here with external libs)
Same with me, I actually had to install Usage to see Fubar show up at all >.< It's one of my lowest users on my setup.
Edit for clarity's sake. I too am using external libs (meaning my libraries are in my MAIN addon folder (World of Warcraft/Interface/Addons/libname), not within the actual addon's folder (World of Warcraft/Interface/Addons/addonname/libs/).
For me, the biggest "hogs" are Ace2, which is used by almost all my addons, and PitBull. Often PeriodicTable chimes in, other then those none of my addons go over 1MB. Ace2 uses around 2 to 3MB, PitBull usually 1 or 1.5MB. My total addon load is tops 30MB.
I think so, but it requires more responsibility for the end-user (updating libraries). The benefit is that you load less during logins and reloads (which takes less time), and there tends to be less conflicts between different versions.
With externals, you have less folders in the /Interface/Addons folder, it means each addon will contain a libs folder with the libraries that addon needs. Result: Wow will load the addon and thus the libs, next addon may have a new version of that lib, Wow loads it again, sees the libs are newer, discards the previously loaded libs, etc until the full loading is done. It will take a fraction more time to load (this isn't always noticeable.)
Without externals, you will have a lot more folders, but you have only one copy of each library, which decreases your load time (not always noticeable as I said). But that is about it.
Which one is better? Decide for yourself, I prefer without externals simply because it seems to load things a fraction faster, but I have a shitload of folders that I have little idea about. So for an end-user not looking into creating addons themselves, it may be beneficial to just use with externals. Do a search on the forums, you will find more topics on this than I care to admit or think about.
Switching the option "No Externals" on in JWoWUpdater (so it downloads the libs into their own folder in /addons/) actually fixed a LOT of errors I was getting with some mods since the update to FuBar 3.0. Only issue I have now is the saving thing which has obviously been reported to Jira. (and some other error about PaladinTimerFu and locale not existing)
Dunno if it hogs alot of memory or not. Don't notice much difference in that window. My top 3 memory hoggers (this during raids) are still Ace2, atlasloot and one more mod that i forgot but its not fubar. (fairly sure it was my bagmod infact)
At most i use around 31mb and that is if i don't give a hoot about doing garbage collection every now and then and cleaning up Violation.
I can't say i like the config menu on Fubar 3.0 much but hopefully it will get a more familiar and simpler ui as time goes. As it is now however, it has enabled me to remove niagara/waterfall as standalone mod configuration panels so less memory to use there (not that it was alot to begin with)