First of all, thanks for commenting on the thread! Also, I really hope it hasn't come across as though this post was "bandwagoning" on the "struggle with getting started with X.js week". The reason I LOVE Backbone is the fact is the fact that it's not opinionated on application architecture.
However, IMO no one (or not many) people build single page todo apps. People have real, multi-state and multi-screen apps that they're trying to build and I think that Backbone site/docs would really really helps people take their understanding of Backbone and architecture to the next level if an example was provided that went beyond the humble Todo app. DOM structure, Zombie events and View management (subviews, etc) are things that I feel are missing, not from Backbone itself, but that Backbone should/could provide as examples of using Backbone to deal with these real, use-case issues that arise.
I think this lack of documentation/examples acted as a catalyst for things like Marionette (hat tip Derick Bailey), but if patterns were outlined from the get-go on the Backbone site, people would be less inclined/feel the need to throw something like Marionette at it.
Hope this has come off as my humble opinion and not just "grumpy developer snark" - I love Backbone but I'd love to see it have an easier route for learning to build real world apps.
I hoped this line "From personal experience, I’ve used APIs heavily with only two languages; JavaScript and PHP." would convey that I'm only going to be talking about these two...
You're right, I think it felt more natural to do it the way I did. If I did it in the above way, then the browser would DL the PNG then the JS would cause the browser to go DL the SVG. As a %, the browsers that do support SVGs are far greater than those that don't. So those people are still getting a great experience, but the SVG supporting browsers getting an even better one!