>At least coming from another SQL database..[].. Yeah, that'd be it. Not everyone comes to Postgres with an understanding of another RDBMS or even SQL; I would

>At least coming from another SQL database..[].. Yeah, that'd be it. Not everyone comes to Postgres with an understanding of another RDBMS or even SQL; I would imagine this guide is designed to reduce the learning curve for those developers who are more likely to pick up a popular NoSQL solution simply because it has more user friendly docs and a data structure they are already used to dealing with, i.e JSON (k:v). HN users seem to agree with the concept "if in doubt, use Postgres" but that is far from the reality out there, especially in those circles not particularly used to handling ops (e.g frontend).