&gt; It was also the single-most decision that made me lose faith in the standards committee.<p>When I try to think of any product or service born of a standards committee that has been wildly successful, I can&#x27;t think of any.<p>Standards committees are useful if the goal is to bring consensus-driven stagnation (and standards), so that things can evolve around a group of products&#x2F;services rather than just individual products&#x2F;services. But, there have been extremely complicated standards like some of those from OASIS: <a href="https:&#x2F;&#x2F;www.oasis-open.org&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.oasis-open.org&#x2F;</a> that made developers waste countless hours trying to adhere when a high level of complexity wasn&#x27;t necessary. And even well-used standards like SQL have not moved quickly enough with the times, e.g. if you look at the differences between the major databases (PostgreSQL, Oracle, SQL Server, etc.), there are still many DB-specific features that could be standardized.<p>&gt; Instead of giving us one of the most well tested SQL implementations (SQL Lite) that addresses all of the above, and much more<p>I wish embedding PostgreSQL would get to the point that people would think of it before SQLite, especially in situations like this that are generic, because there is so much more that could be done with it. Here&#x27;s one recent effort in Java: <a href="https:&#x2F;&#x2F;github.com&#x2F;yandex-qatools&#x2F;postgresql-embedded" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;yandex-qatools&#x2F;postgresql-embedded</a> and a slidedeck from a few years ago from the postgres lead at VMWare with that team&#x27;s experience: <a href="http:&#x2F;&#x2F;www.slideshare.net&#x2F;jkshah&#x2F;pg-conf-eu2013embedded" rel="nofollow">http:&#x2F;&#x2F;www.slideshare.net&#x2F;jkshah&#x2F;pg-conf-eu2013embedded</a>