Subject | Making the Leap of Faith to Firebird. |
---|---|
Author | sharkboy_nz |
Post date | 2005-03-31T01:30:23Z |
Hi All,
My company develops and markets a Delphi application, which currently
uses IB6 at the back end.
We've made the decision to jump (step) from IB6 to Firebird because of
the age of IB6, assorted platform issues with it and because of the
lightweight security.
However the potentially short turnaround between Firebird V2 and V3
has created an issue for us.
In short, we don't want to commit to V2, and then find that it's
orphaned by V3. At the same time we aren't that comfortable about
committing to V3 and running the risk that the release date slips so
much that it's no longer useful for our project.
Understand that we have 4000 remote installations of IB6 to convert,
so the cost of preparing an installation routine and deploying is
significant.
There's also the issue of having to deal with concurrency issues
between IB6 and Firebird. (Mitigated in V3.0 I know, but when?)
At the moment we are tending towards committing to V2 now, and
assessing V3 in Q3 05.
Do you think this is this a practical approach?
What will become of V2.0 if V3.0 is an early success?
How can I obtain some reassurance that recommending Firebird V2 won't
affect my future "employability"?
TIA
Mark.
My company develops and markets a Delphi application, which currently
uses IB6 at the back end.
We've made the decision to jump (step) from IB6 to Firebird because of
the age of IB6, assorted platform issues with it and because of the
lightweight security.
However the potentially short turnaround between Firebird V2 and V3
has created an issue for us.
In short, we don't want to commit to V2, and then find that it's
orphaned by V3. At the same time we aren't that comfortable about
committing to V3 and running the risk that the release date slips so
much that it's no longer useful for our project.
Understand that we have 4000 remote installations of IB6 to convert,
so the cost of preparing an installation routine and deploying is
significant.
There's also the issue of having to deal with concurrency issues
between IB6 and Firebird. (Mitigated in V3.0 I know, but when?)
At the moment we are tending towards committing to V2 now, and
assessing V3 in Q3 05.
Do you think this is this a practical approach?
What will become of V2.0 if V3.0 is an early success?
How can I obtain some reassurance that recommending Firebird V2 won't
affect my future "employability"?
TIA
Mark.