Jeff Davis wrote:
> Keep in mind that backwards compatibility is not the only issue here;
> forwards compatibility matters as well*. A lot of the encoding issues I
> wrote up ( http://wiki.postgresql.org/wiki/Driver_development ) will
> probably be real bugs in a python3 application using a driver that
> doesn't understand encoding properly.
>
Sure, but the benefit of being the de-facto standard to some problem,
because you're already supported by everybody, is that it's easier to
attract the most help to move forward too. The disclaimers on
investments always read "past performance is not indicative of future
results". I don't think that's really true in the open-source project
case. Generally, I'd rather trust a project that's been keeping up with
things for a long time already to continue to do so, particularly one
that's built up a community around it already, rather than risk
switching to one without a known good track record in that record.
(Exercise for the reader: consider how what I just said applies in both
a positive and negative way toward MySQL and its associated development
model)
--
Greg Smith 2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
greg@2ndQuadrant.com www.2ndQuadrant.com
