Fork me on GitHub

@plexus: @borkdude one issue about not using #route is that you're relying on some server to do the rewriting for you. In practice you're always downloading the same files so why not package it as an application you run by downloading a single executable (index.html) I think the server side part is especially troubling when things should work offline. Unless you want isomorphic rendering I don't see a strong reason to use /route instead of #route


they have different semantics, right? if you want links that people share to specific locations in your app, then you're best not to use fragment identifiers. People have a habit of not copying anything after #, we noticed this at my last job. Also IIRC Safari drops the part after # when following redirects, which means any URL shortener will already mess things up


@plexus: wow that Safari thing is strange (but true)


> People have a habit of not copying anything after # do they? I'd expect people to just copy everything but I also don't have any empirical evidence to back that up. Maybe also a different thing the # comes right after the domain


yeah, we actually observed this. sites add so much crap after ? and #, mostly for keeping track of analytics metadata, that people learn to ignore it


also, not surprised about anything in Safari anymore, it truly is the new IE


see for example, where (str ...) misbehaves in Safari 6.0.5, and lacking a cross-browser solution nothing happens, which seems at least partly at fault for why printing a js/Symbol causes a TypeError in ClojureScript


@plexus: the problem with safari being the new IE is that chrome is still a massive resource suck in OSX. It makes me sad, but I actually use it, because when I'm working in a cafe somewhere I don't like to give away 2 hours of battery life for a better browser...