31–40 of 182 posts
When I started using Django 10 years ago during the Django/Rails era, Postgres was by far the most recommended DB to use. Not sure if that was also true in Rails community.
Postgres became cool when the scales fell off peoples eyes and they realized that very few use cases necessitate or even benefit from "NoSQL" databases.
It was way before that - it was when people got fed up with the string handling and implicit type casting stupidity of MySQL
Hmm for me when Oracle bought MySQL.
Strange how people seems to have forgotten that.
Postgres became cool when the scales fell off peoples eyes and they realized that very few use cases necessitate or even benefit from "NoSQL" databases.
It was way before that - it was when people got fed up with the string handling and implicit type casting stupidity of MySQL
I run Postgres since about 2016. I used to run MySQL behind the same frontend app. I barely know anything about Postgres beyond installation for our use case, backup and recover. I used to know loads about obscure MySQL optimization techniques, fixing broken tables, fiddling with scary parameters and recovering from hair raising situations. I like my current state of ignorance.
I love not having to be trivia king.
When I started using Django 10 years ago during the Django/Rails era, Postgres was by far the most recommended DB to use. Not sure if that was also true in Rails community.
~2011 I remember people religiously recommending postgres over mysql. ~2009 it seemed the go to db was still mysql.
When I looped back around several years later Postgres had started to overcome MySQL. Conventional wisdom then was it was roughly at feature parity with MySQL but more robust.
So it would seem that working on having a robust inner core first paid off, even if it cost some early reputation.