I've been streaming on and off for a few years now. Livecoding was a good idea in principal, but the team did not handle their growth well, and made a few prett

I've been streaming on and off for a few years now. Livecoding was a good idea in principal, but the team did not handle their growth well, and made a few pretty bad decisions which have been well documented on HN before. Twitch didn't ever feel like it was the right place for programming streams, but it's the best we have right now. I hope I can get back into streaming later on in the year (it's quite a big time commitment), perhaps there will be a better solution by then! My wish-list: A good chat API which supports code snippets (this is something that streamers will want to pour over and make streams about, because it makes good content!). Localized streaming servers in order to keep latency low. The site development process should be streamed! I have no idea why the Livecoding guys didn't live stream their dev work (other than perhaps a fear of losing "IP", but I personally don't think that's a particularly strong argument - there's always some code that could be streamed without issue, such as frontend JS. I suspect the real reason was that their developers weren't aligned with the product and didn't want to stream). Support for pair programming (two streamers working on the same project together) - this allows streamers to market to each others' audience, and can produce some really great content as the streamer is forced to explain to their partner why they're doing what they're doing. Integration with editors as an alternative to regular streaming. A UI which looks something like jsbin.com - where the text editor is shown next to the output - would allow for streamers with lower upload speeds to only stream their webcam, while their editor and terminal is mirrored in text, nicely resizing to fit the users' screens. This view could be composited into a video stream for users who aren't viewing through a web browser (like chromecast users).