Understand The Web by Ben Ward
benward.me
benward.me
The use of the window.location.hash property to support linking to content within apps has been hit and miss in the last few years with web apps. Many times the back and forward buttons don't work, bookmarking a particular hash doesn't go back to that content on refresh, or there is no hash change for content at all.
The right constraints are a good thing, because they allow you to sacrifice flexibility in exchange for useful guarantees. In programming languages, constraints like "no shared mutable state" offer guarantees like referential transparency and thread safety. In user interface design, constraints can offer consistency and interoperability. In network architecture, constraints like "no connection state" offer guarantees that benefit horizontal scalability.
Bullshit. Whether you like it or not "the web" has come to mean both the original application itself: a collection of hypertext documents, images, etc; as well as the greatest application deployment platform we've seen (and those applications may or may not have anything to do with hypertext)
These two things can coexist. Give me a different name and I'll start using it.
The web, with its interconnectedness, happens to be a pretty good tool for distributing content. Applications tend to be tools for manipulating content. So we get web applications: tools for manipulating content that you can find or create on the web. The problem comes when web applications start to bite the hand that feeds, by isolating the content within the application from the rest of the web.