Earlier quoted context omitted.
Winamp ( winamp ) It really whips your browser's ass.
My brain automatically read that in that guy's voice from DEMO.MP3, complete with the bleating.
LOL same. It's absolutely wild how that's an automatic response.
Winamp source code leak
111–120 of 338 posts
Re: Winamp source code leak
#112Honest question, as someone who actually used Winamp back in ~2004: why would you want to use it now? I have some nostalgia for it, sure, but what exactly does it actually offer you that something like VLC doesn't? It seems like it plays my music and videos competently enough, and I don't know anyone who actually uses Shoutcast anymore. This isn't a passive aggressive dig or anything, I would actually like to know.
It's basically a perfect music player. Lightweight, fast, runs on every version of Windows 95+, great playlist manager, skins, and has extensive plugins which support any music file format.
Why continue the search for perfection once it's been found?
Re: Winamp source code leak
#113Earlier quoted context omitted.
I never get how Archive.org can get away with... everything? Like every single console game is there. Nintendo is very famous to take down ROM sites yet their full library is on Archive.org. And that's Nintendo only, all the PS1, PS2, PS3 games and the whole Xbox/360 catalog is there as well. It's crazy In some aspect Archive.org is better than some private torrent trackers
I've been worrying about this as well. I recently found a Beetles discography on Archive.org even after TPB turned up almost nothing. It's great being able to find things, but It'd be a shame to loose all of the legitimate content because of getting associated with blatant piracy.
Meatspace libraries often have a big collection of CDs too. This is part of our cultural heritage, and I think making it accesible in this form is a no-brainer.
(By the way, maybe it was a typo, but the spelling is "Beatles". They were better at songwriting than puns.)
Re: Winamp source code leak
#114I nearly got a job with them back around 2001. At the time they were revamping their development group. I had written some plug-ins for Winamp so I familiar with the plug-in structure. It looks like the new lead developer wanted to rewrite everything. Using all kinds of object-oriented methodologies. The older code was all C based and very simple. I wasn’t fan of the new direction.
> the new lead developer wanted to rewrite everything. Using all kinds of object-oriented methodologies. The older code was all C based and very simple. A tale as old as time.
Is it bad that I start hearing the Aladdin (1992) soundtrack whenever I read that line?
Re: Winamp source code leak
#115Interesting as a historic document. If someone is willing to port it to newer systems or compilers, also maybe of some value. I really don't see much value considering there are already reasonable good, lightweight (I think) and multi-platform (like qmmp) which offer support to winamp skins.
It's the same as the Opera Presto leak a few years ago. You cannot legally maintain or update, let alone distribute it. Back then you could find a few minor patches in Russian forums but that's about it. So even if there's people capable and willing to maintain it (which for a browser I think is an order of magnitude more work), there is no easy way to have a collaboration platform that also gives the project enough…
Is this legal obstacle true everywhere? If a company stops making a breakfast cereal permanently, then I can replicate it and sell my own. Why not a browser that Opera is never going to sell again?
Re: Winamp source code leak
#116Winamp was still my music player of choice until a little over a year ago when I finally made the switch to MusicBee.
My hero. If I was not on Linux I feel like I'd be on the same boat. On Linux I use mocp which is a console-based directory-based player, so pretty much the same thing.
Weirdly, mocp always led to memory leaks for me on Lubuntu.
These days I mostly listen to soma.fm (you can use mplayer for their feeds[0]) or youtube in browser
[0] A small gist I am super proud of as I don't write much bash: https://gist.github.com/tomrod/0b5caceec1a10acfb134aefb5fd85...
Re: Winamp source code leak
#117I still remembers all those crazy music visualizations. It was rarely seen these days. Someone should make a WebGL version.
Re: Winamp source code leak
#118Interestingly enough, there has been a community project dedicated to keeping the last Winamp version alive (last version from the original creators), and it really great to use. https://getwacup.com/ It includes a skin that allows it to work on modern display resolutions. It's really interesting to see just how low-res screens were when it was in it's hey-day, given that they are nearly unusable on a 4k monitor. Edi…
XMMS was a really nice Winamp clone for Linux way back when. Might be a good starting point.
Re: Winamp source code leak
#119Interestingly enough, there has been a community project dedicated to keeping the last Winamp version alive (last version from the original creators), and it really great to use. https://getwacup.com/ It includes a skin that allows it to work on modern display resolutions. It's really interesting to see just how low-res screens were when it was in it's hey-day, given that they are nearly unusable on a 4k monitor. Edi…
> It includes a skin that allows it to work on modern display resolutions. It's really interesting to see just how low-res screens were when it was in it's hey-day, given that they are nearly unusable on a 4k monitor.
Monitor size/resolution has gotten larger which is some of the factor but I think people downplay the shift in common effective DPI which leads to a much bigger perceived change in UI sizing design than there really has been. In the late 90s to early 2000s an effective DPI of 75-85 for a typical home user was not uncommon. Nowadays an effective DPI of 125-135 is pretty standard, many tech folk using an effective DPI of 150 because it gives the effect of having more workspace.
So what may have looked like a half physical inch wide UI element on a standard user's display in the late 90s might look like a quarter inch wide UI element on many HN reader's screens today because nobody likes to set their DPI properly :p.
Re: Winamp source code leak
#120I just can’t understand the point of the DMCA takedown here. This software is very dead and abandoned at this point, and the only thing bearing its name is vaporware that appears to be so distant from the original as to effectively not even compete with it.
Of course, the copyright holders have every legal right to do so. But doesn’t it seem pointless? This codebase probably has more historical interest than commercial by now. Am I missing something?