| Subject | RE: [IBO] Promoting IBO (was: Re: IBO advantages over IBX) |
|---|---|
| Author | Dion Oliphant |
| Post date | 2001-01-08T23:56:24Z |
I am sure it was more faith than hunch!
D.
-----Original Message-----
From: Jason Wharton [mailto:jwharton@...]
Sent: 09 January 2001 01:23
To: IBObjects@egroups.com
Subject: Re: [IBO] Promoting IBO (was: Re: IBO advantages over IBX)
worse (kind of).
Ravi Kumar stole my class names that I was using for my TDataset based
components. I had already been production and had customers using those
classes. I noticed at a BorCon presentation that he showed the class names
he chose, the same as mine, and made sure that he was aware that he was
heading in to claimed territory. At that time there was nobody relying on
his work at all. It was purely in an alpha state of development. He
acknowledged the conflict and said he would see what he could do about it. I
trusted that he would do the responsible and respectful thing and didn't
press the issue much harder. To my surprise a year later when Inprise
decided to release the BETA of IBX he had not changed the class names.
By doing this I could no longer install IBO into the IDE without
uninstalling IBX. Not only would people be prevented from using them in the
same program but there would be a serious problem with installation, etc.
So, what else could I do? My customers and I had to make lots of changes...
It was rather painful to have to change class names. I didn't have GReplace
at that time...
I had a friend who was trying to get me to go after Inprise in a lawsuit. He
had a lawyer all lined up to take them to the cleaners for damages. They had
everything prepared to nail them for it. But, I decided it wouldn't be in
the interest of the greater whole to do such a thing. Turns out my hunch was
absolute right.
That isn't to say I didn't feel horribly abused and taken advantage of. I
just thought it wasn't prudent to do such a thing. For all I know, knowing
now what Bill Karwin was going through back in those days... Inprise would
have flushed InterBase down the toilet rather than get hard hit with a nasty
lawsuit. Bill and I had a chat and he said that if I had done this it would
have really made matters for InterBase survival worse.
Anyway, this is perhaps why I have such a disdain for IBX. It was a really
sore spot and still is to some degree. I just about decided to kill the IBO
"commercial" arm and just stick to using it as an in-house tool while
continuing to support those who already became my customers. But, a strong
hunch told me to hang in there and stay with things and I am very glad that
I did.
Things are continuing to look up for IBO and InterBase. I am truly excited
to see what this year has in store.
Regards,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com
D.
-----Original Message-----
From: Jason Wharton [mailto:jwharton@...]
Sent: 09 January 2001 01:23
To: IBObjects@egroups.com
Subject: Re: [IBO] Promoting IBO (was: Re: IBO advantages over IBX)
> Thinking about this, it came to my mind that there was once a discussionOk, I remember now what you are probably alluding to. It wasn't code but
> about the fact (?) that the programmer of IBX (not Jeff) has taken some
> code from IBO and used it for IBX.
worse (kind of).
Ravi Kumar stole my class names that I was using for my TDataset based
components. I had already been production and had customers using those
classes. I noticed at a BorCon presentation that he showed the class names
he chose, the same as mine, and made sure that he was aware that he was
heading in to claimed territory. At that time there was nobody relying on
his work at all. It was purely in an alpha state of development. He
acknowledged the conflict and said he would see what he could do about it. I
trusted that he would do the responsible and respectful thing and didn't
press the issue much harder. To my surprise a year later when Inprise
decided to release the BETA of IBX he had not changed the class names.
By doing this I could no longer install IBO into the IDE without
uninstalling IBX. Not only would people be prevented from using them in the
same program but there would be a serious problem with installation, etc.
So, what else could I do? My customers and I had to make lots of changes...
It was rather painful to have to change class names. I didn't have GReplace
at that time...
I had a friend who was trying to get me to go after Inprise in a lawsuit. He
had a lawyer all lined up to take them to the cleaners for damages. They had
everything prepared to nail them for it. But, I decided it wouldn't be in
the interest of the greater whole to do such a thing. Turns out my hunch was
absolute right.
That isn't to say I didn't feel horribly abused and taken advantage of. I
just thought it wasn't prudent to do such a thing. For all I know, knowing
now what Bill Karwin was going through back in those days... Inprise would
have flushed InterBase down the toilet rather than get hard hit with a nasty
lawsuit. Bill and I had a chat and he said that if I had done this it would
have really made matters for InterBase survival worse.
Anyway, this is perhaps why I have such a disdain for IBX. It was a really
sore spot and still is to some degree. I just about decided to kill the IBO
"commercial" arm and just stick to using it as an in-house tool while
continuing to support those who already became my customers. But, a strong
hunch told me to hang in there and stay with things and I am very glad that
I did.
Things are continuing to look up for IBO and InterBase. I am truly excited
to see what this year has in store.
Regards,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com