A Reimplementation of Winamp 2.9 in HTML5 and JavaScript • Hacker News Board

Re: A Reimplementation of Winamp 2.9 in HTML5 and JavaScript

#111

Post by captbaritone » Fri, Feb 09, 2018, 12:35 AM UTC

jihadjihad wrote: post #75

laumars wrote: post #61

Earlier quoted context omitted.

Shoutcast and the real-time visualisations are two killer features Winamp had that I don't think any media player since has even come close to competing with. I'm not saying there aren't still decent media players out there, but honestly I think Winamp is still the best there's ever been.

I completely agree, nothing came close to the awesomeness of Milkdrop 2 in Winamp. That's one of the reasons I got into programming, by being curious about how it "knew" how to move to the music. Still have it installed on an ancient PC, will never delete it!

Have you seen https://butterchurnviz.com ?

Re: A Reimplementation of Winamp 2.9 in HTML5 and JavaScript

#112

Post by kuschku » Fri, Feb 09, 2018, 12:41 AM UTC

msie wrote: post #84

greymeister wrote: post #25

Earlier quoted context omitted.

I always used skins in Winamp/XMMS, but I'm immediately filled with nostalgia upon seeing the default skin. I wonder if people who came to use computers in the last decade will experience the sort of enjoyment I got out of customizing the look and feel of applications. All of the walled gardens have intertwined design with functionality to the point where skinning doesn't really exist in the same way. I haven't used…

It looks harder to completely replace the Windows shell than before. I've looked long and hard for a replacement that looks like Windows 95 (menus and windows controls especially) but no luck. There is WindowShades but it doesn't completely replace everything.

Don't worry, KDE for Windows is still a thing - although the "whole shell" replacement currently isn't working with KDE Plasma 5, but only KDE 4

Re: A Reimplementation of Winamp 2.9 in HTML5 and JavaScript

#113

Post by dang » Fri, Feb 09, 2018, 12:42 AM UTC

TomMarius wrote: post #72

dictum wrote: post #42

Earlier quoted context omitted.

Unfortunately, even proficient developers are having trouble due to some misguided technical choices those websites are making: https://twitter.com/sindresorhus/status/900005504931438593

Why exactly misguided? Because it doesn't allow you to hack their site? Uh... Edit: read the FAQ, downvotes are not for disagreement.

That's not in the HN FAQ. Downvoting for disagreement has always been allowed here. Some historical links at https://news.ycombinator.com/item?id=16131314.

Commenting about downvotes in arguments isn't ok, though: https://news.ycombinator.com/newsguidelines.html.

Re: A Reimplementation of Winamp 2.9 in HTML5 and JavaScript

#114

Post by taytus » Fri, Feb 09, 2018, 12:45 AM UTC

_diyu wrote: post #13

Wow, it even has skin support! I spent way too many hours developing skins for WinAmp and Trillian back in the late 90s as a teenager. I get why skins fell out of style, but I also kinda wish they didn't. Choosing a skin lets you personalize an app, creating a skin does so even more while also letting you express your creativity, and having skins creates a community. If I ever make an app where skinning would make se…

I wonder why we are not skinning websites 🧐

Re: A Reimplementation of Winamp 2.9 in HTML5 and JavaScript

#115

Post by dsl » Fri, Feb 09, 2018, 1:04 AM UTC

Avery3R wrote: post #64

captbaritone wrote: post #18

Earlier quoted context omitted.

Unfortunately, you can never fully work. DRM means we can’t get raw access to the audio stream so EQ, visualization, balance, (for example) won’t work.

You can use a virtual audio cable. Spotify -> virtual cable -> winamp -> real audio out

Can you recommend a "virtual cable" javascript library that is compatible with DRM output? I can't seem to find anything.

Re: A Reimplementation of Winamp 2.9 in HTML5 and JavaScript

#116

Post by mrits » Fri, Feb 09, 2018, 1:11 AM UTC

The wiki says Winamp was created in 1997. I feel like I used it in 94 or 95.

Re: A Reimplementation of Winamp 2.9 in HTML5 and JavaScript

#117

Post by ghostcluster » Fri, Feb 09, 2018, 1:17 AM UTC

mrits wrote: post #116

The wiki says Winamp was created in 1997. I feel like I used it in 94 or 95.

It was released in late April 1997. MacAmp actually came out a little earlier on April 13, 1997

Re: A Reimplementation of Winamp 2.9 in HTML5 and JavaScript

#118

Post by digi_owl » Fri, Feb 09, 2018, 1:32 AM UTC

Not sure if should be impressed or appalled.

These days i think i'll just use Foobar2k on Windows, and Deadbeef (or a terminal player) on Linux.

Re: A Reimplementation of Winamp 2.9 in HTML5 and JavaScript

#119

Post by digi_owl » Fri, Feb 09, 2018, 1:38 AM UTC

taytus wrote: post #114

_diyu wrote: post #13

Wow, it even has skin support! I spent way too many hours developing skins for WinAmp and Trillian back in the late 90s as a teenager. I get why skins fell out of style, but I also kinda wish they didn't. Choosing a skin lets you personalize an app, creating a skin does so even more while also letting you express your creativity, and having skins creates a community. If I ever make an app where skinning would make se…

I wonder why we are not skinning websites 🧐

Could have sworn that browsers have the capability to load custom CSS. But then writing CSS may well be a full time job, so...

Re: A Reimplementation of Winamp 2.9 in HTML5 and JavaScript

#120

Post by digi_owl » Fri, Feb 09, 2018, 1:39 AM UTC

_diyu wrote: post #13

Wow, it even has skin support! I spent way too many hours developing skins for WinAmp and Trillian back in the late 90s as a teenager. I get why skins fell out of style, but I also kinda wish they didn't. Choosing a skin lets you personalize an app, creating a skin does so even more while also letting you express your creativity, and having skins creates a community. If I ever make an app where skinning would make se…

Used to be a thing on Linux DEs, but then one of the major interface libs kept screwing around with their themeing APIs...