I'm excited about this as I am a heavy SoundCloud user but I can't help but feel this post is a bit premature. The existing state of the 'next' site is really early.. there are many bugs, most features are not implemented, and the sound detail page is almost completely broken.
I'd must rather see these kinds of posts after a big rewrite has proven the new technologies were the right choice!
The main reason is quite obviously for feedback. SoundCloud is a community-driven site, and we want to get really early feedback about features, design, etc. Another part of the feedback is exactly what's happening here with sharing our techniques and seeing the results. Hopefully the outcome of this blog post is that some other people will learn something, but also that some people will point out things so that we ourselves can learn.
> there are many bugs, most features are not implemented,
We're definitely aware of the features not yet implemented, but if you find bugs (or are really missing a particular feature), please do use the feedback form to let us know!
I've been using the feedback feature early and often (nice job putting it so front and center also!)
I think the new design and architecture is coming out great and I don't mean to discourage experience sharing. If anything, better way to have said would be:
I hope that you will post a few follow-ups to this as you get closer to release what/if anything has changed in your stack, approach, and gotchas found building this complex of a single page/backbone app.
I'd must rather see these kinds of posts after a big rewrite has proven the new technologies were the right choice!