This article is only about localStorage as a cache for performance optimization, and fails to signal this clearly enough. If, instead, you want to use it to store things locally (for example, persist a blob of data across page reloads), I assume it could be a fine solution.
There also seems to be something not quite pinned down about the argument that localStorage hits the disk on every access, and is therefore slow, especially since another argument is that if you "never visit a web site again, the data is still loaded when you start the browser." I'm a performance-conscious web developer, but is it really on me to carefully keep the browser from hitting disk? It's possible but it sounds suspect.