Subject | Re: [IBO]Major problem for me with V4.7.16 |
---|---|
Author | George |
Post date | 2007-02-20T09:24:19Z |
--- In IBObjects@yahoogroups.com, "Jason Wharton" <supportlist@...>
wrote:
I don't mean to understate your achievement in IBObjects - usually
products on this scale could reasonably be expected to be supported
and developed by a team rather than a single resource and I am sorry
if I seem not to appreciate your work because I do.
Whilst this is not the forum for a debate about the commercial
realities of software development, we both know that testing is
carried out to an extent that matches perceived risk and fits within
available budgets, even the biggest houses will not routinely test to
the nth degree. (If you did there would be little need for this
forum).
We have to constantly weigh the risks, costs and benefits when
deciding how deep to test and we all do it differently - Microsoft is
a good example .... well no more of that.
Suffice to say I see little quality alternative to using OBjects but
we will probably wait a while.
Many thanks for your constructive responses.
George Elton
wrote:
>very valid.
> George,
>
> ......... These are real costs and real impacts. Your point is
>I've
> However, these things are standard procedure in every software shop
> ever had employment at. With any new release of a product which ispart of
> an interdependant group of tools, testing and user impact should bea top
> priority prior to any production release.exceedingly
>
> It took me quite a bit longer (3 months or so) to make IBO work
> well with Firebird 2 and I could complain about it but rather I seeFirebird
> becomming a much better product overall and it has forced IBO toalso become
> a much better product overall. I had to pass some of this work onto my
> customers but I am certain those who fully understand the need fortrue
> progress in information technology and simply take it head-on; theirreality in
> products will also be much better overall as well. It's just a
> our industry that we need to be as responsible and responsive aspossible to
> a fast changing/evolving development environment. The ideals youseek are
> money and management savers but they would be very expensive interms of the
> progress they would hamper.our
>
> > It is a problem for us and we will monitor the situation before
> > making a final decision.
> >
> > I would welcome any comments or assurances in this area.
>
> Hopefully what I've shared gives you an idea of our philosophy and
> commitment to balance these two aspects as best we can.Jason
>
> Regards,
> Jason Wharton
>
I don't mean to understate your achievement in IBObjects - usually
products on this scale could reasonably be expected to be supported
and developed by a team rather than a single resource and I am sorry
if I seem not to appreciate your work because I do.
Whilst this is not the forum for a debate about the commercial
realities of software development, we both know that testing is
carried out to an extent that matches perceived risk and fits within
available budgets, even the biggest houses will not routinely test to
the nth degree. (If you did there would be little need for this
forum).
We have to constantly weigh the risks, costs and benefits when
deciding how deep to test and we all do it differently - Microsoft is
a good example .... well no more of that.
Suffice to say I see little quality alternative to using OBjects but
we will probably wait a while.
Many thanks for your constructive responses.
George Elton