They definitely need some js error tracking tool (like qbaka.net) to handle errors. Their main javascript size is 420K!

Thanks for the recommendation. We (I am in the TouchDevelop team) have an excellent crash tracking system in place, and whatever issues you see today might be fixed tomorrow. If you are curious how we build TouchDevelop, you can watch this video from a session at the recent Build conference: http://channel9.msdn.com/Events/Build/2012/3-018

Having seen the first announcement of TouchStudio (the previous name for Touchdevelop) on MSDN and installed it on my WP7 phone, I can attest that the development team is constantly improving and updating the project.

My only beef with the WP7 version is that the increases in integration with online content have at times disrupted fluidity by delaying loading of portions of the app.

It is great to see HN finally giving the project some deserved attention. Previous submissions regarding the project have fallen flat.

Thanks and keep up the good work.

Thank you for the link. I am curious and will try to find an hour to watch the video. Do you mind if I contact you by email (already googled it) to ask some questions about your error tracking? It seems that you do not use window.onerror so I wonder how exactly you track unhandled errors. Your experience may help me with my project.

Sure, send me an email. We might be missing out on some errors, appreciate any kind of feedback, and maybe can give some advice too.

Which browser/platform?

Windows , Chrome 24.