Re: MuPAD bugs: series can return 6 terms only

From: Richard Kanarek (FirstInitialLastName_at_Spamcop.net)
Date: 02/24/05 

Date: Thu, 24 Feb 2005 04:24:40 -0500

Greetings,

I can't say that I agree with your (rather harsh) assessment of Mr.
Bondarenko.

Although I'm sure he can state his reasons better than I can, it would
appear that Mr. Bondarenko's efforts are "motivated" by a particular
dislike of CAS software defects ("bugs") and a particular fondness for
the automated method he developed (and is marketing?) for detecting
defects.

I think that castigating Mr. Bondarenko for not "reporting" bugs is
wholly incorrect. I don't see how Mr. Bondarenko, who is presumably
not employed by one of the CAS producers, can be considered obligated
to report their bugs in strict accordance with their rules. Further,
posting reports of the bugs here ought to be enough. If a little (?)
company/group like Sciface, or at least an occasional
employee/associate/(indentured grad student <g>) can bother to stop by
every now and again, surely someone from the other companies could be
bothered to too.

Lastly, I'm glad that Mr. Bondarenko's loose cannon has swung around
to MuPAD. I'm currently a reasonably "happy" MuPad user/Sciface
customer. If Mr. Bondarenko can help keep SciFace focused on quality
improvements, while warning me of current problems, I can only get
happier.

On Thu, 24 Feb 2005 00:12:52 GMT, Patrick Hamlyn
<path@multipro.N_OcomSP_AM.au> wrote:

>Will Twentyman <wtwentyman@read.my.sig> wrote:
>
>>Vladimir Bondarenko wrote:
>>
>>[bug report number who knows what]
>>
>>Serious question: why are you posting these here instead of reporting
>>them to the people in charge of the MuPAD project?
>
>Kinda obvious isn't it.... he's trying to push an agenda. 'Damage the reputation
>of various computer algebra systems publically' rather than 'improve various
>CASs by reporting bugs'.
>
>The real question is why he's bothering...

Relevant Pages

  • Re: MuPAD bugs: series can return 6 terms only
    ... Although I'm sure he can state his reasons better than I can, ... I think that castigating Mr. Bondarenko for not "reporting" bugs is ... I'm currently a reasonably "happy" MuPad user/Sciface ...
    (sci.math.symbolic)
  • Re: 2.6.19 -mm merge plans
    ... I actually expected people to dislike arbitrary rules more than they do, but I've come to believe that people _like_ having rules that they have to obey, as long as it's not a big pain for them. ... So I think that a "odd release"/"even release" rule that clarifies what a certain mid-point in the release cycle actually _means_, even if it doesn't necessarily add anything else, might be a good thing. ... Then after people stop reporting show stoppers, change to rc numbers, where rc versions are actually candidates for release without known major bugs. ...
    (Linux-Kernel)
  • Re: Inheritance
    ... Go hooking to fix bugs in MS code? ... There's no site for reporting bugs in VS ... >> always be using the latest DDK. ... Maxim Shatskih, Windows DDK MVP ...
    (microsoft.public.development.device.drivers)
  • Re: First day with production development on D2005
    ... >> involved in reporting them vs. the benefit of reporting them. ... > The cost is taking some time to write the report. ... bugs are unlikely to get fixed and that show-stopper, ... not bother reporting bugs and if the development environment has too many ...
    (borland.public.delphi.non-technical)
  • Re: Wolfram Alpha claims to be a primary source.
    ... D> But your manner of reporting bugs, ... D> newsgroups in a dramatic way is not the best approach. ... It's probably not an unreasonable assumption that had Vladimir been professional about the way he reported bugs, he may well have been considered for employment by Maplesoft, Wolfram Research, perhaps Mathworks too. ...
    (sci.math.symbolic)