> Also source code is pointless without dev(s)
Given the number of people still interested in Winamp, I'm sure there would be people willing to work on it if it were open-sourced.
I meant no offense :-)
Re:WinAmp Community Update Project
by thedoctor_o on Thursday February 10, 2022 @11:54AM
(#30288977)
No offence taken. I would just rather than waiting around for those many willing devs (most of which seem to be web devs rather than native client devs from my past 8yrs experience) to appear I've instead put my time & effort into making something as I was already doing for the decade before Winamp was eventually sold on.
So as long as I end up with WACUP being a program that fulfils my needs in allowing my plug-ins to keep working & happens to be of use to others wanting a supported native 'classic' winamp experience (due to the pivot from a plug-in pack to being a standalone player) then I'm going to keep doing it irrespective of what is / isn't happening with "winamp" (I don't view anything that now comes out as being winamp other than a brand name slapped onto some code).
-dro
Re:WinAmp Community Update Project
by EMIRELADERO on Wednesday February 09, 2022 @10:51PM
(#30282263)
I believe the above commenter was speaking more from a place of nostalgia and curiosity, rather than "usability".
As you've clearly got something that fits your needs as do I by slowly making my own Winamp compatible player to run my old Winamp plug-ins (which were always closed source nor am I for or against OSS but it needs to be the dev that decides not external pressure) because I don't trust nor like what's happened with those that now own the brand.
Also source code is pointless without dev(s) & unless we're looking for AI to do all of the coding, whether the code is open or closed, the fleshy meat bag bashing the keyboard is still needed for the time being :)
Use what makes you happy & I'll keep making & using what makes me happy too :)
-dro