When trying to port my web app into a Chrome app I had to rewrite all localStorage to be async because the Chrome app localStorage was async ... After a few wee

When trying to port my web app into a Chrome app I had to rewrite all localStorage to be async because the Chrome app localStorage was async ... After a few weeks I gave up as there was too much work to make it into a Chrome app, but I kept the storage async in the web app. It seems that CPU memory is the new RAM and RAM is the new HDD, so it makes sense to make everything that access RAM async ... But then when everyone use async abstractions like "futures" it becomes a net negative in performance.