RE: jaws 5.1

  • From: "jim grimsby" <jimgrims@xxxxxxxxxxx>
  • To: <jfw@xxxxxxxxxxxxx>
  • Date: Thu, 6 May 2004 17:56:40 -0700

No in the paying software world they have some thing called the preview
version Microsoft uses this system to provide user with new features
faster they only go in to beta after they have most of the features
worked out. Most previews are alpha software.  They offer no support
what so ever for preview and bugs are sent to an email address witch is
never replied to.  These bugs ard added to the data bass for the testers
to test.  It is then up to the user to determent for him self wither or
not he wants to preview the software.  The jfw public beta is similar
but you get the software much latter in the game.  It seems like I said
before that the users of today want and like what is going on so I will
withdrawal my original point and concede that I was wrong to bring it up
in the first place for it seems the majority of users are happy with the
currant system.  I my self remember a very different world of access
where we needed the access so much that we were willing to preview the
software and help make corrections.  Where field testing was the thing.
Where everyone wanted a peace of the action in making the screen reader
better.  Where the bug reports were read with custo where people would
go out of there way to reproduce them and yes we took the risk at the
work place because we new that we had to test these things in the real
world and even though there were some bugs we wanted to use the latest
and greatest and we did not want to be left behind.  Where the leaders
of the company answered every question and if a bug was find it was
fixed asap and a new release came and if another bug was found then
again another maintance release. I guess I am the only person unhappy
with the new access order where you never see the reps on the list.
Where you don't get a update every two weeks or so.  Where we flew by
the seet of our pants. Remember it was this world that brought you
windows access back in 1992 in June of 1992 infact.  Perhaps I am just a
greasing symbolic son maybe. Well they say grief take time to deal with
maybe the two year has not been enough. 
Well I went on a tangent here I intended only to correct the original
poster incorrect assumption that only free software has unsupported
versions.   Take care and enjoy the new access order where you have no
say and some else gets to decide what you have access to. 

-----Original Message-----
From: jfw-bounce@xxxxxxxxxxxxx [mailto:jfw-bounce@xxxxxxxxxxxxx] On
Behalf Of Sean McMahon
Sent: Thursday, May 06, 2004 2:52 PM
To: jfw@xxxxxxxxxxxxx
Subject: Re: jaws 5.1


In the free software world, they have some feature which are called
unsupported usually in unstable versions of there product.  They refer
to them as development versions.  This only works because you have the
tools to fix them you have access to there source.  Not something under
jaws.  Jaws should only allow access to experimental features for free.
That is if they want to continu charging for the final product.
----- Original Message ----- 
From: "jim grimsby" <jimgrims@xxxxxxxxxxx>
To: <jfw@xxxxxxxxxxxxx>
Sent: Thursday, May 06, 2004 1:48 PM
Subject: RE: jaws 5.1


>
>
> -----Original Message-----
> From: jfw-bounce@xxxxxxxxxxxxx [mailto:jfw-bounce@xxxxxxxxxxxxx] On 
> Behalf Of david poehlman
> Sent: Thursday, May 06, 2004 1:25 PM
> To: jfw@xxxxxxxxxxxxx
> Subject: Re: jaws 5.1
>
>
> You've lost me hree but I'll try to pick up the thread.  The idea 
> behind getting a new release out the door is two fold.  To put new 
> features in it and improve what is tere and to meet deadlines.  If 
> remote access bcomes available under these constraints, it does.  You 
> don't throw an untested feature into a product just to get it in 
> before it goes out the door because it is just a sloppy thing to do 
> and causes lots of problems on both the developer side and the 
> customer side. You do if people need it what you do is you put it out 
> there and let the user know that it is available but is not being 
> supported at this time. And so for those of us who need it will have 
> it.  Perhaps I should remind the users who feel that stability is the 
> most important thing here is this.  Your screen reader is your only 
> means of getting access. If you have to wait a year to be able to do 
> the same things your sighted counterparts are doing then you are going

> to be unable to keep up and be competitive.  In my work as a fre lance

> support person I find that the home user is using the latest software 
> and if I can not advice them on what to do with it then I am out of a 
> job.  Granted I do not get much work in this line as of now but the 
> work I do get depends on me being able to access all of the latest and

> greatest toys. SO I disagree I would rather have some access even if 
> it is problematic then no access. Some is always better then none and 
> that is the choice.  What I am saying here is put the power in the 
> users hand if you have a timid user then so be it he can be timid and 
> not take the risk.  If you have a real user who is willing to take the

> risk then let him or her do so. You will get a lot more feed back and 
> you will see a lot more testing in the field.  In my mind a good 
> access product is one that give you access as fast as possible.  The 
> second thing that makes it good is  correcting the bugs as they 
> accore. You do not sacrifice speed for stability and that is the trend

> I see happening in the access world to day.  It did not used to be 
> like this how-ever.  If access was possible no matter what the bug you

> got it.  And documentation was provided on known bugs. That is the way

> it should be again.  Remember a new version of windows is coming out 
> soon and we will need to be on the cutting edge of it if many of us 
> want to be productive.  Well I have said my last on this subject for I

> can see that view points are set in stone and there is no reviving of 
> the dead and gone.
>
>
> --
> 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
>

--
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


--
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: