From: | vinny <vinny(at)xs4all(dot)nl> |
---|---|
To: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
Cc: | Paul Hughes <paul(at)vivation(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)postgresql(dot)org, pgsql-general-owner(at)postgresql(dot)org |
Subject: | Re: Python versus Other Languages using PostgreSQL |
Date: | 2017-05-09 11:44:03 |
Message-ID: | eac8951181e6a04bffc2667f2c6dd210@xs4all.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2017-05-09 11:26, Francisco Olarte wrote:
> Paul:
>
> On Tue, May 9, 2017 at 2:45 AM, Paul Hughes <paul(at)vivation(dot)com> wrote:
>> ....My question still remains though - why is it that all the largest
>> web platforms that have used PostgreSQL *specifically* choose Python
>> as their back-end language?
>
> Do you have any data supporting that? AFAIK people tend to choose the
> language first, database second, not the other way round, and many
> times the platform language is nailed, but the db can be changed.
In fact, I don't think many companies/developers even choose a language
or database, but rather just use whatever they have experience in.
>
>> Why are Postgres and Python so married, in the same way that Node.js
>> is largely married to MondogDB?
>
> I do not think either of these is true.
>
Perhaps not in real world applications, but the vast majority of
tutorials etc certainly
connect PHP to MySQL, Node to Mongo and Python to PostgreSQL.
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2017-05-09 13:26:21 | Re: data transformation and replication |
Previous Message | Neil Anderson | 2017-05-09 10:35:32 | Re: Python versus Other Languages using PostgreSQL |