News for hackers. Stuff that matters.
Re:Postgres is eating the database world by vsnf on Friday March 15, 2024 @06:32AM (#39714025)
That feels a bit like hindsight talking. Linux perhaps, but were Python and Postgres really the obvious good judgement choices 25 years ago? Every other choice was poor judgement?
Re:Postgres is eating the database world by slyall on Friday March 15, 2024 @07:34AM (#39714364)
Well 25 years ago was pretty much (December 1998) when "LAMP"[1] was defined and that was originally Linux, Apache, MySQL and PHP.

So Postgres and Python were not the obvious choices back then.

[1] https://en.wikipedia.org/wiki/LAMP_(software_bundle)

Re:Postgres is eating the database world by Shish2k on Friday March 15, 2024 @08:47AM (#39714917)
In my personal experience of being around back then, postgres and python were still considered "technically better", but such a massive pain in the ass to install (especially on cheap shared hosting where it was often actually impossible to install) that only the most masochistic people would even try. I myself wrote a fastcgi implementation in PHP which would allow a web server which only supported php to call python under the hood and forward the inputs and outputs :P

It is kind of depressing that 25 years later, no other language has even attempted to compete with PHP in the “easy to get started on bargain-basement-tier shared web hosts” space D:

Re:Postgres is eating the database world by dagw on Friday March 15, 2024 @10:34AM (#39716212)
no other language has even attempted to compete with PHP

PHP has been very good at reinventing itself and being its own biggest competitor. Zend outcompeted PHP3, PHP5 outcompeted PHP4, PHP7 outcompeted PHP5 and so on. Compare a site written in modern idiomatic PHP8 using something like Laravel to a site written in classic PHP3 and they might as well be two different languages.

Re:Postgres is eating the database world by The_Colonel on Friday March 15, 2024 @02:47PM (#39719279)
IIRC the big break was betweem PHP 4 and PHP 5, they had very different object model. Otherwise the it's not that different.
Re:Postgres is eating the database world by spacebanana7 on Friday March 15, 2024 @11:24AM (#39716790)
It's amazing how that's not a terrible choice of tech stack even today after 26 years.

Not fashionable by any means - but still feasible to maintain unlike Windows IIS / C++ or Oracle / Perl / Flash.

Re:Postgres is eating the database world by pg_1234 on Friday March 15, 2024 @03:13PM (#39719596)
Still, by 15 years ago Linux, Nginx, Postgres, Python had become a clearly better choice than the default LAMP stack for more complex applications.
Re:Postgres is eating the database world by antifa on Sunday March 17, 2024 @12:13PM (#39735452)
That's how you airdrop straight into the worst of the python 2 3 fiasco, probably the worst time in history to start using python, meanwhile when Ruby on Rails and Java were probably the kings of that era.
Re:Postgres is eating the database world by taffer on Friday March 15, 2024 @04:11PM (#39720170)
Postgres really took off when Heroku became popular in the late 00s.
Re:Postgres is eating the database world by fulafel on Friday March 15, 2024 @01:04PM (#39717983)
MySQL didn't have transactions (for many years after that), so PG over MySQL would have been the case for "good technical judgement" though maybe not the majority choice. For Python, maybe I'm biased - but you could have went for PHP in the argument if you swing that way and it still works.
Re:Postgres is eating the database world by djupblue on Friday March 15, 2024 @04:21PM (#39720280)
Around 20 years ago when I was trying to decide on what database to use my requirement were that it should store data reliably. I learned that MySQL in contrast to PostgreSQL: 1. wasn't ACID 2. didn't have foreign key constraints 3. could loose/corrupt committed data (no WAL)

Despite me not knowing much about databases it seemed like an obvious choice.

Re:Postgres is eating the database world by Tostino on Saturday March 16, 2024 @01:02AM (#39723516)
Hell, 10 years ago (in a multi database project) I got bit by MySQL not supporting check constraints, but returning successfully when I ran the create check constraint statements.

Postgres has been great all around.

Re:Postgres is eating the database world by derekperkins on Saturday March 16, 2024 @05:02PM (#39729439)
It finally supports them, which is nice. It doesn't support deferred checks to the commit, like postgres, but are otherwise good. I've appreciated using it to enforce json schema at the db level