| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Ryan Pedela <rpedela(at)datalanche(dot)com> |
| Cc: | "Shulgin, Oleksandr" <oleksandr(dot)shulgin(at)zalando(dot)de>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, hlinnaka <hlinnaka(at)iki(dot)fi> |
| Subject: | Re: [PATCH] Generalized JSON output functions |
| Date: | 2015-07-16 17:51:05 |
| Message-ID: | CA+TgmoZpRyR2mgKRsCW10_d5yAe2GFHchJn7UWWTtbmRFJ6RWw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jul 15, 2015 at 1:10 PM, Ryan Pedela <rpedela(at)datalanche(dot)com> wrote:
> Like I said previously, the
> situation with Javascript will hopefully be remedied in a few years with ES7
> anyway.
I don't understand these issues in great technical depth, but if
somebody is arguing that it's OK for PostgreSQL to be difficult to use
for a certain category of user for several years until the next
language rev becomes mainstream, then I disagree. The fact that
somebody wrote a patch to try to solve a problem means that the thing
in question is a problem for at least that one user. If he's the only
one, maybe we don't need to care all that much. If his needs are
representative of a significant user community, we should not turn our
backs on that community, regardless of whether we like the patch he
wrote, and regardless of how well we are meeting the needs of other
communities (like node.js users).
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2015-07-16 18:00:23 | Re: [PATCH] Generalized JSON output functions |
| Previous Message | Robert Haas | 2015-07-16 17:45:16 | Re: [PATCH] Generalized JSON output functions |