> So is PHP according the infallible SV pundits Sarcasm is unnecessary but I'll admit that so is the word "cancer". Your first example is a great one, althoug

> So is PHP according the infallible SV pundits Sarcasm is unnecessary but I'll admit that so is the word "cancer". Your first example is a great one, although the catalog would have to be really huge to not fit in memory; and since it is static (the users don't update it) it can be upgraded by downloading a json file regularly? The second example doesn't explain why you would need a relational db. Anyway my point is not to second guess applications that run well, and even less to argue with people who have already mastered IndexedDB -- good for them! My point is for people on the fence to take a good, hard look at what's possible with localStorage and make sure that before they embark on the IndexedDB voyage, they are absolutely, positively certain that they have no other choice. I recently came across an app that stores a couple of user preferences on IndexedDB; the funny part is that the comments complain for paragraphs about its quirks and general unpleasantness. The time spent complaining in the source would have been better spent switching to localStorage.