Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A Reimplementation of Winamp 2.9 in HTML5 and JavaScript

github.com

Post reply on HN
Print view View original

51–60 of 212 posts

Re: A Reimplementation of Winamp 2.9 in HTML5 and JavaScript

#53

Post by asdfgadsfgasfdg »

captbaritone wrote: post #18
mortenjorck wrote: post #16

Earlier quoted context omitted.

Implementing this looks like it would be a fun project: https://github.com/JMPerez/spotify-web-api-js You'd still need the Spotify desktop client open (Winamp2-js would function as a remote), but you could do things like populating the playlist window with a user playlist.

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.

Pretty sure you can get it for visualization...

Re: A Reimplementation of Winamp 2.9 in HTML5 and JavaScript

#54

Post by Raphmedia »

_sdegutis wrote: post #37
mi100hael wrote: post #28

Earlier quoted context omitted.

Honestly, skinning is probably easier today than it ever has been. With custom client-side stylesheets, there's no reason someone couldn't roll out custom skins for sites like Facebook, Twitter, etc.

I bet there's branding and usability reasons for Facebook to avoid allowing you to skin/theme it to the extent Winamp was skinnable. Not sure I know what those are, but I just really doubt they'll ever add that feature.

Facebook is optimized to get you addicted to your feed. Muted blue colors everywhere with contrasting bright "berry red" rewarding notifications. Images that are always more contrasted than the layout, etc.

Anecdotal: I use a custom Facebook skin that makes the whole UI red and add a background image. Since I've started using it, I spend less time on the website. It feels, in a way, more tiring to use the custom theme.

Re: A Reimplementation of Winamp 2.9 in HTML5 and JavaScript

#56

Post by j45 »

vvanders wrote: post #36
bhauer wrote: post #29

Amazing. Wishful thinking: If this included something akin to Shoutcast (perhaps via WebRTC), it would give us back the peer-to-peer listening joy we had for small groups and teams back in the day. I miss the era when things were more commonly/naturally peer-to-peer and decentralized.

Shoutcast was amazing, I can easily credit it to opening up my music horizons to bands that just weren't played on the radio at the time(euro-metal/etc \m/ \m/). To this day I find Spotify and its competitors a poor substitute, algorithms still can't match a well curated station.

Shoutcast / icecast still is amazing. Still running a few environments and they perform great.

If you're looking to tune in to something, I like http://www.somafm.com, possibly the original spotify / coding playlist. (BeatBlender, etc)

Re: A Reimplementation of Winamp 2.9 in HTML5 and JavaScript

#58

Post by laumars »

mi100hael wrote: post #28
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…

Honestly, skinning is probably easier today than it ever has been. With custom client-side stylesheets, there's no reason someone couldn't roll out custom skins for sites like Facebook, Twitter, etc.

Just because the client-side application's source code is readable in a text editor it doesn't mean it's easier to skin than a binary blob who's theming support is documented.

Not to mention how your method could break tomorrow without warning because Facebook (or whatever you're skinning) push out an update that's incompatible with the theme you've hacked on to it.

Post reply on HN