Hi guys,
Not sure if Peter was joking, but Ian's approach sounds much more
user-friendly.
Getting Oracle users to convert to PostgreSQL then be "stuck-with-it"
because they can't afford the migration elsewhere is not the right
approach.
PostgreSQL is a really good product, and the best way to emphasise it is
"here's PostgreSQL, people use it coz it *works better*".
And that's definitely achieveable.
:)
Regards and best wishes,
Justin Clift
Ian Lance Taylor wrote:
>
> Peter Eisentraut <peter_e@gmx.net> writes:
>
> > Tom Lane writes:
> >
> > > Now now, what about our goal of Postgres world domination? Gonna be
> > > tough to get there unless we can assimilate Oracle users ;-)
> >
> > In order to achieve world domination you don't want to offer
> > compatibility, otherwise your users could move back and forth easily.
> > What you want is static conversion tools so people can move to your
> > product but not back to others.
>
> I disagree. To achieve world domination you should lower to barriers
> to adoption as much as possible, and then keep people with you due to
> the superiority of your product. If the barriers to adoption are
> high, people won't take the risk, and won't discover the superiority.
>
> Incompatible syntax is a barrier to adoption because people fear the
> time required to learn the new syntax, and they fear adopting Postgres
> and then discovering after three months of enhancements to their
> Postgres code that Postgres won't do the job and they have to switch
> back.
>
> Ian
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
--
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there." - Indira Gandhi