Originally Posted by Aminifu
(I was tired and maybe a little cranky earlier)
likewise at the time and i guess it doesn't help i probably care too much about inane little things when i probably shouldn't, oh well.
back to the points about memory usage, i'm really not sure on how the nde databases like is used for the history tracking deals with memory as i'm not sure if it's just keeping a copy of changed values or a complete image (which i'd doubt) or something else. as i've never really bothered to look at the underlying code (not needed to), i cannot really answer such questions.
however, from http://forums.winamp.com/showpost.ph...0&postcount=93
and the few posts before it, i am starting to think something isn't right somewhere though i'm not sure where since the test i'm still running has history and a few other aspects disabled to rule them out affecting the Source DSP but i'm now 5hrs later than that post and Winamp's using almost 4Mb more. but like in the post, i'm more concerned about the handle count which is almost 7 times what it was when i started which was ~450 though it could even be one of my plug-ins at fault (which would be amusing).
i will now answer how i take it for the following comment
The problem, as I see it, is why do the powers that be for Winamp deem a lot of what should be done as "things which would officially be deemed as unimportant / not worth the resources". Do they view the desktop as dead and mobile as the only important thing?
i think it most likely comes down to return of investment vs time spent as is going to be the case with most things. since some of the random little bugs i've fixed over the years have taken on/off a few weeks to track down which only affected a small proportion of users which financially couldn't have been warranted. obviously in an ideal world there should be no bugs or a means to immediately look into it but that's never how Winamp has ever really worked.
and yes there is more of a focus on the Android and Mac apps compared to the desktop which is going to rub desktop only users the wrong way but supposedly 'mobile' is the money making future if everything is to be believe - personally i don't know and as i don't even have a smart phone or need to get one i'm really not the target audience for such things.
but really i do not know what the focus / intention of things is be it just letting the desktop version stagnate or just ditching it as is and going all new without any of the legacy issues like the app versions don't have to deal with (though obviously that then kills all of the plug-ins and gets back into the 2.x vs 5.x issues or where people won't upgrade because of a plug-in which is 12 years old won't work with anything current).
as i think i've said before, Winamp is unfortunately hindered by it's past success and related legacy aka the Windows dilema. then again maybe it would be good to just start things fresh and do it properly but then that's also got its own cost implications and would a user base accept such a thing? probably not or at least not the user base who've kept using it over the years.
then again, i think there are ways to keep with the current plug-in setup and way that Winamp works without going from scratch such as with the case of new apis have always been added over time, it would just mean more formalisation of any newer apis to be better designed / implemented than what has gone before and just map legacy api's to be wrappers around the new functionality - ideal example of this from previous updates is the file converter api which has changed a few times but still maintains the older interface for those using it.
if anything, the more pressing thing i think is trying to ensure a consistent UI experience irrespective of the skin being used - ideal example is the tooltip text for the playlist buttons for Modern vs Bento which do the same thing but the text is different. or like how some of the library plug-ins supporting certain ways of showing the default key for an action and changing it as needed whereas other ones just don't both to do it. but then is that an issue with different people having worked on different parts and never done the utmost to ensure a consistent method and way of doing things over the 14+ years as we're now at.
and of course, would it even be Winamp without all of these quirks and inconsistencies and the like.