Live data from Hacker News

A Reimplementation of Winamp 2.9 in HTML5 and JavaScript

github.com

101–110 of 212 posts

Re: A Reimplementation of Winamp 2.9 in HTML5 and JavaScript

#101
post #91

Author here. I wrote a Twitter thread demonstrating many of its features. You can find it here: https://mobile.twitter.com/captbaritone/status/9612747140133...

This is great and brings back a lot of old memories. Something that would help this spread (perhaps if it was hosted somewhere dedicated to it), is allowing a URL of an MP3 or a list of other audio files to be included in the link so people can share a song "the way it was meant to be played." Thanks for your hard work and for making sure it wasn't broken in Edge. It was really satisfying to pull it up on my Windows…

Alas, this is more complicated than just including a link. The mp3 needs to be served with permissive "CORs" headers, and most are not. I made the call, that it would be too confusing for users to try to support loading from URL.

Re: A Reimplementation of Winamp 2.9 in HTML5 and JavaScript

#102
post #89
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…

sorry to be the party pooper, but saddly, allowing skins kind of forfeits your control over the ui & design of your app doesn't it

The dev still has the power to choose the default; the user just has the ability to veto it. That sounds like a massive positive, from the user's perspective.

Re: A Reimplementation of Winamp 2.9 in HTML5 and JavaScript

#104
post #98
post #92

Just says "Loading ..." for me when using SlimJet? Chrome works.

Here is the same thing, the errors are: TypeError: Object.entries is not a function(…)e.(anonymous function) @ console.js:32 Skin.js:127 Uncaught (in promise) TypeError: Object.entries is not a function(…)

Could you paste a full stack trace?

Re: A Reimplementation of Winamp 2.9 in HTML5 and JavaScript

#105
post #89
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…

sorry to be the party pooper, but saddly, allowing skins kind of forfeits your control over the ui & design of your app doesn't it

So? An app isn't meant to hang in a museum and look pretty for the developer.

If the end user thinks it would be better with a different font or larger text or a different background, then they're right.

And realistically once an app ships to the end user the developer has forfeited all control anyway.

Re: A Reimplementation of Winamp 2.9 in HTML5 and JavaScript

#106
post #8

Winamp + dialup connection. How many hours have we lost downloading a bunch of mp3 files...

Dialup? Lucky. I had 14.4k through my dad's Startac until I was about 15.

You had the internet through a mobile phone and you're calling dial up lucky? Mobile phones were legit space age back then.

Re: A Reimplementation of Winamp 2.9 in HTML5 and JavaScript

#107
post #91

Earlier quoted context omitted.

This is great and brings back a lot of old memories. Something that would help this spread (perhaps if it was hosted somewhere dedicated to it), is allowing a URL of an MP3 or a list of other audio files to be included in the link so people can share a song "the way it was meant to be played." Thanks for your hard work and for making sure it wasn't broken in Edge. It was really satisfying to pull it up on my Windows…

Alas, this is more complicated than just including a link. The mp3 needs to be served with permissive "CORs" headers, and most are not. I made the call, that it would be too confusing for users to try to support loading from URL.

Yeah, that makes sense. You would have to download the remote resource in the link and re-host it which can get expensive quickly. There are probably a few scenarios where DNS tricks would save the day, but not reliably.

Re: A Reimplementation of Winamp 2.9 in HTML5 and JavaScript

#110
post #91

Author here. I wrote a Twitter thread demonstrating many of its features. You can find it here: https://mobile.twitter.com/captbaritone/status/9612747140133...

This is great and brings back a lot of old memories. Something that would help this spread (perhaps if it was hosted somewhere dedicated to it), is allowing a URL of an MP3 or a list of other audio files to be included in the link so people can share a song "the way it was meant to be played." Thanks for your hard work and for making sure it wasn't broken in Edge. It was really satisfying to pull it up on my Windows…

Regarding Edge, all credit goes to the work the Edge team has put into the browser. I just made sure I was building to spec, and it seemed to work!
Post reply on HN