Echo JS 0.11.0

<~>

mxxx 9 days ago. link 1 point
Funny that this should get re-posted, I ran into a bunch of problems with localStorage in a production app just recently; a certain group of our users were unable to use localStorage (seems like some sort of content policy issue) and as a result some of our functionality was failing. 

The odd thing about that particular article though is he recommends falling back to in-memory storage, which isn't really the same thing at all, since it doesn't persist across sessions (which is generally the point of localStorage, no?)

Potentially you'd be better off using something like localForage which attempts to use other APIs, or even a cookie-based fallback.