RE: Eric Damery's response to my Blog comments
- From: "Chip Orange" <Corange@xxxxxxxxxxxxxxx>
- To: <jfw@xxxxxxxxxxxxx>
- Date: Tue, 26 Jun 2007 10:01:47 -0400
It's not fair, nor polite, for you to smugly point out that someone
doesn't know as much about programming as you do Barry. Do you want me
to start arguing that I know more about programming than you do, and so
your opinion is therefore completely invalid?
And as for your comparison to Microsoft, well, do they make users
constantly pay for bug fixes? The same ones that you point out that
come every month?
In my opinion, bug fixes should *always* be at no cost, and should be
separated from feature enhancements so that users can pay for
enhancements as they want them, and so they can get the correctly
working product that they thought they were buying in the first place.
Mixing bug fixes with feature enhancements forces users to buy features
they didn't necessarily want just to get the bugs fixed.
Chip
------------------------------
Chip Orange
Database Administrator
Florida Public Service Commission
Chip.Orange@xxxxxxxxxxxxxxx
(850) 413-6314
(Any opinions expressed are solely those of the author and do not
necessarily reflect those of the Florida Public Service Commission.)
> -----Original Message-----
> From: jfw-bounce@xxxxxxxxxxxxx
> [mailto:jfw-bounce@xxxxxxxxxxxxx] On Behalf Of Barry Campbell
> Sent: Monday, June 25, 2007 7:07 PM
> To: jfw@xxxxxxxxxxxxx
> Subject: RE: Eric Damery's response to my Blog comments
>
> Cris:
> obviously you know little about computer programming my
> friend. Speaking
> as someone who has written programs for over 24 years I can
> tell you that
> the more responses with as much information as possible helps
> a lot. I
> believe Freedom is as discouraged as the users are. When you
> believe you
> have fixed the problem and it tested out in the shop and with
> a limitted
> number of testers but then it reappears again. Please give
> Freedom as much
> info as possible and from as many types of systems, operating
> systems and
> settings. It is a bug that is very complex I think and
> eventually they will
> nail it down. For the others who think that freedom is wasting SMA's
> solving this problem you are quite incorrect. All you have
> to do is look at
> the what's new for each version that comes out. They are
> fixing as much as
> possible and adding new features as the market demands. All
> software is not
> perfect look at Microsoft who patches windows each month.
>
>
>
>
> -----Original Message-----
> From: jfw-bounce@xxxxxxxxxxxxx
> [mailto:jfw-bounce@xxxxxxxxxxxxx] On Behalf
> Of Chris Skarstad
> Sent: Monday, June 25, 2007 6:06 PM
> To: jfw@xxxxxxxxxxxxx
> Subject: Re: Eric Damery's response to my Blog comments
>
>
> Hi. Ok, all this sounds well and good, but if we keep reporting the
> same issues to the tech support people and they either don't listen
> or respond, or just keep telling people to do the same uninstall,
> re-install steps over and over, and it doesn't seem to work, what
> then? I'm fully aware that it's really hard to reproduce a problem
> that just a few people are having, and if someone has a problem
> under one operating system yet it doesn't happen on another that's
> not an easy bug to squash. But at the same time, giving the same
> canned responses is not the answer. and what if you've done all this
> before you've even called them and the problem still persists? doing
> it again, over and over and over obviously isn't helping and the tech
> support people who are giving these responses need to be made aware
> that this method isn't working. They talk about wanting to give us
> the highest quality tech support and the best product possible, what
> company doesn't? But this stuff is happening and they need to do
> something about it, I mean, really do something about it and make
> their customers happy again.
>
>
>
>
>
>
>
> At 04:35 PM 6/25/2007, you wrote:
> >
> >Rick,
> >
> >The main concern and request I have is that if you are experiencing
> >problems, and the release of 2173 did not completely resolve them
> >for you, is that you
> >would please report them into our support with the best possible
> >detail. As always, we will do our best to work through the issues
> >with you and all the
> >customers who are reporting such issues. The Virtual Buffer is in IE
> >and OE were very bad for those that experienced them. The same for
> >the crashing issue
> >in OE which you and some others experienced. We got them reported,
> >got details from as many of the users with the issues, and went back
> >to the those customers
> >with updated versions to verify that we resolved it. I recall doing
> >exactly that on the OE crashing issue with you many months ago when
> >I saw it being
> >reported on a list server.
> >
> >Since you have installed 2173, you pointed out to me on the phone
> >today that the Virtual Buffer issue has all bug gone away compared
> >to 2107 and earlier.
> >You mentioned that you did get one on the Audible Site Saturday and
> >maybe one on Thursday I guess also, which may have led to the
> >negative posting on Darrell's
> >Blog Thursday night. This to me says there may still be something
> >going on but as I mentioned to you today, it is difficult to solve
> >what we can't reproduce.
> >It does not mean we will not continue to work the issue, but getting
> >the reports to our support team with the best step to step details
> >will go further
> >to helping solve the issues than anything else.
> >
> >I've taken the time to respond to you (along with Jeff and Darrell),
> >because your customers and I'm hoping we can continue to deliver you
> >all the best quality
> >product possible, just as we attempt to do for all customers. I hope
> >that this email serves to resolve your issues and open up
> >communication between you
> >and support to further improve the product. It is not my intention
> >to debate these issues on your blog or podcasts.
> >
> >Eric
> >
> >-------------------------------------------------------------
> ----------
> >---------
> >
> >=======
> >
> >Visit my webpage and podcast feed at:
> ><http://www.blind-geek-zone.net>http://www.blind-geek-zone.net
> >and my web Blog at:
> ><http://blind-geek-zone.blogspot.com/>http://blind-geek-zone.
> blogspot.c
> >om/
> >
> >
> >__________ NOD32 2353 (20070625) Information __________
> >
> >This message was checked by NOD32 antivirus system.
> ><http://www.eset.com>http://www.eset.com
>
> --
> JFW related links:
> JFW homepage: http://www.freedomscientific.com/
> Scripting mailing list:
> http://lists.the-jdh.com/listinfo.cgi/scriptography-the-jdh.com
> JFW List instructions:
> To post a message to the list, send it to jfw@xxxxxxxxxxxxx
> To unsubscribe from this mailing list, send a message to
> jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the
> subject line.
> Archives located at: //www.freelists.org/archives/jfw
>
> If you have any concerns about the list, post received from
> the list, or the
> way the list is being run, do not post them to the list.
> Rather contact the
> list owner at jfw-admins@xxxxxxxxxxxxxx
>
> --
> JFW related links:
> JFW homepage: http://www.freedomscientific.com/
> Scripting mailing list:
> http://lists.the-jdh.com/listinfo.cgi/scriptography-the-jdh.com
> JFW List instructions:
> To post a message to the list, send it to jfw@xxxxxxxxxxxxx
> To unsubscribe from this mailing list, send a message to
> jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the
> subject line.
> Archives located at: //www.freelists.org/archives/jfw
>
> If you have any concerns about the list, post received from
> the list, or the way the list is being run, do not post them
> to the list. Rather contact the list owner at
> jfw-admins@xxxxxxxxxxxxxx
>
--
JFW related links:
JFW homepage: http://www.freedomscientific.com/
Scripting mailing list:
http://lists.the-jdh.com/listinfo.cgi/scriptography-the-jdh.com
JFW List instructions:
To post a message to the list, send it to jfw@xxxxxxxxxxxxx
To unsubscribe from this mailing list, send a message to
jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.
Archives located at: //www.freelists.org/archives/jfw
If you have any concerns about the list, post received from the list, or the
way the list is being run, do not post them to the list. Rather contact the
list owner at jfw-admins@xxxxxxxxxxxxxx
Other related posts:
