Subject | Re: [IBDI] PHOENIX IN ASCENDANT |
---|---|
Author | Mark O'Donohue |
Post date | 2000-07-29T08:13:37Z |
Hi Helen
I would certainly be happy using a NewCo'ed interbase (could that be a Nuked
interbase database). And may be able to lend a hand for some of the linux and
java stuff. Im currently crawling through trying to get the linux source
compiled.
A while ago people were musing about creating a new database from scratch. To
some degree that is no longer required. The core components are at least
available, and although it is only half a promise at least we have that to
start with.
In the short term NewCo would need to build some credibility and market
presence, presumably it has an ODBC driver and can mirror the current
source/binaries. (I could think of some interesting licencing conditions for
that ODBC driver).
However, at some point in the medium to long term, I believe there will have
to be a reconciliation (lets be tactful and call that capitulation) from
Borland/Imprise and a resolution of the forked source/test suite/documentation
issues. I personally think that if Inprise keep up the current good work then
NewCo may even be able buy the bits at (hopefully a bargin price) from
whatever company Dale actually sells Borland to.
I'm at a bit of a distance, but I don't think Dale's ego is the main problem,
he's just bending to where he can get dollars and media exposure. I think
that the interest in interbase since it's opensource announcement has started
him or others wondering about what they actually have in interbase. And
rather than opensourcing it just to placate irate existing
customers/developers, now he/they are trying to twist the opensource thing a
bit to perhaps make some more money out of it.
If a new name is needed for a forked product here are some contributions:
NewCo SQL Server
Phoenix SQL/Relational Server
GInterBase
Groton Database
StarkeyBase
WolfBase
Jim (As in startrek) Base
AnnBase
Disinterbase
FullerBase (FullerBaseLess, BaseLessFuller)
Cheers
Mark
I would certainly be happy using a NewCo'ed interbase (could that be a Nuked
interbase database). And may be able to lend a hand for some of the linux and
java stuff. Im currently crawling through trying to get the linux source
compiled.
A while ago people were musing about creating a new database from scratch. To
some degree that is no longer required. The core components are at least
available, and although it is only half a promise at least we have that to
start with.
In the short term NewCo would need to build some credibility and market
presence, presumably it has an ODBC driver and can mirror the current
source/binaries. (I could think of some interesting licencing conditions for
that ODBC driver).
However, at some point in the medium to long term, I believe there will have
to be a reconciliation (lets be tactful and call that capitulation) from
Borland/Imprise and a resolution of the forked source/test suite/documentation
issues. I personally think that if Inprise keep up the current good work then
NewCo may even be able buy the bits at (hopefully a bargin price) from
whatever company Dale actually sells Borland to.
I'm at a bit of a distance, but I don't think Dale's ego is the main problem,
he's just bending to where he can get dollars and media exposure. I think
that the interest in interbase since it's opensource announcement has started
him or others wondering about what they actually have in interbase. And
rather than opensourcing it just to placate irate existing
customers/developers, now he/they are trying to twist the opensource thing a
bit to perhaps make some more money out of it.
If a new name is needed for a forked product here are some contributions:
NewCo SQL Server
Phoenix SQL/Relational Server
GInterBase
Groton Database
StarkeyBase
WolfBase
Jim (As in startrek) Base
AnnBase
Disinterbase
FullerBase (FullerBaseLess, BaseLessFuller)
Cheers
Mark