51–60 of 90 posts
looks awesome. two questions: 1) which technologies was used? 2) how do you handle high loads?
I considered using amazon for scaling but the article below this one says amazon is down, hehe.
Earlier quoted context omitted.
I'm guessing you have javascript turned off? Otherwise the songs should just play instantly.
Why, oh why does such a site require Javascript?! edit: I'm not against requiring Javascript for those parts of your website that absolutely, positively require it, but everything that can work without JS should gracefully degrade.
What am I not getting?
Damn that turtle is bad ass.
Looks good. I'm confused about how playlists work though - I can add songs to it, but how do I play it or view it? A killer feature that songza is missing is the ability to create and share a playlist without logging in. edit: Another problem: since you are getting the music from remote sources, they can stick in HTTP authentication headers. I got hit with a few of those. Not sure if there is a practical technical so…
The playlist can be viewed with right-click mouse button. Just added that to the site text :)
It's pretty good - one of the better music index services I've used. Others here have commented on a few small issues but overall it seems well executed. However, is this really a viable business? I assume you intend it to be, based upon your description of it being a startup, but please correct me if I'm mistaken. Otherwise, I'm afraid I'm going to have to piss on your parade a little bit. I have considered developi…
Earlier quoted context omitted.
Why, oh why does such a site require Javascript?! edit: I'm not against requiring Javascript for those parts of your website that absolutely, positively require it, but everything that can work without JS should gracefully degrade.
I didn't downmod, but I don't agree that everything that can work without JS should gracefully degrade. That seems like a lot of extra work to support a miniscule segment of fussy purists. What am I not getting?
I think it's better to express as much as you can in a more "constrained" language like HTML or CSS because it's more like data than code, so it offers less opportunities to make a big mess of spaghetti code and having obscure interactions in the code. It's easier to reason about. HTML and CSS, being declarative, are much easier and cleaner to deal with than JS (it's more WYSIWYG).
So I guess what I'm saying is, coding in a style that avoids JS as much as possible is beneficial, and that style facilitates graceful degradation. Conversely, keeping an eye on graceful degradation will facilitate a better style.
