Subject | Re: [IBDI] Re: [IB-Architect] EasySoft ODBC Driver & Borland |
---|---|
Author | Nick Gorham |
Post date | 2000-09-04T19:58:14Z |
Jason Wharton wrote:
is little from being gained in arguing about what happened. But as I was in the
meetings with Paul at the time, I came away with the feeling (possibly
mistaken) that NewCo needed something ASAP, so I started work on the driver, the
commitment seemed firm, but then again I am a programmer, and may not understand
the subtle issues of sales and marketing :-). After NewCo shifted to do it them
self's I was told to stop work on it, and forget it. It was only after the NewCo
deal seemed to not be providing a driver, I quietly started work on the driver
in my spare time, eventually plucking up courage to mention that it was almost
ready to the CEO.
With this in mind, the phrase "quickly tried to get something to show" does seem
a bit unfair, I think I spent more time getting the InstallShield install
working as I did adding to the driver.
There driver is there, people can try it and make up their own minds about it.
I would hope that people who know my work on unixODBC know that my commitment to
Open Source development and free ODBC implementation goes beyond this driver,
and predates all of NewCo and the current situation.
--
Nick Gorham
"I wish there was a knob on the TV to turn up the intelligence,
There's a knob called brightness, but it doesn't work."
- Eugene P. Gallagher
> >From what I understand, and I surely could be mistaken, the verbal exchangesWell its hard to comment when people seem to have differing recollections, there
> were exploratory, not committal. For whatever reason it was deemed unwise to
> commit to EasySoft under the terms and timeframe they presented. But when
> NewCo shifted to do it themselves EasySoft didn't want to see a market
> segment gobbled up so they quickly tried to get something to show to keep
> their foot in the door. I'm glad they are deciding to commit efforts to this
> because the InterBase market can only be benefited by additional ODBC
> drivers.
>
is little from being gained in arguing about what happened. But as I was in the
meetings with Paul at the time, I came away with the feeling (possibly
mistaken) that NewCo needed something ASAP, so I started work on the driver, the
commitment seemed firm, but then again I am a programmer, and may not understand
the subtle issues of sales and marketing :-). After NewCo shifted to do it them
self's I was told to stop work on it, and forget it. It was only after the NewCo
deal seemed to not be providing a driver, I quietly started work on the driver
in my spare time, eventually plucking up courage to mention that it was almost
ready to the CEO.
With this in mind, the phrase "quickly tried to get something to show" does seem
a bit unfair, I think I spent more time getting the InstallShield install
working as I did adding to the driver.
There driver is there, people can try it and make up their own minds about it.
I would hope that people who know my work on unixODBC know that my commitment to
Open Source development and free ODBC implementation goes beyond this driver,
and predates all of NewCo and the current situation.
--
Nick Gorham
"I wish there was a knob on the TV to turn up the intelligence,
There's a knob called brightness, but it doesn't work."
- Eugene P. Gallagher