That's a good point - still you'd be sacrificing product development speed for the low level fs access, so the author should really make sure they know how much of it they'll need.
It is the blind claim of it being "plenty fast" that is resonated in this thread that I find problematic. The article describes how to implement queueing/app locks/pub sub, without providing any benchmarks on how the same implementations compare to redis under different loads.
If you are using redis and you don't care about perf you are probably doing it wrong. If you are using postgres and you care about perf you are probably doing it wrong. "Probably" because context is key.
If you want to prototype quickly and reuse a component libraries/be able to attract contributors go with Electron. if you need to run your app on low-power devices consider QT but it will require a lot more investment from your end.
Sometimes I wonder what kind of apps you are all developing where using postgres instead of redis makes sense? do you have 3 people using your app? Is 800ms latency ok for your users? Or is it that you don't care. Honest question.