there is nothing to agree or disagree with here. If you have a screen reader and it's the only one that you can use and it crashes your computer every 5 wseconds, guess where it will wind up? We are not beta testers, we pay for a product and we should get our money's worth. If you want that level of release, you may want to look into becoming a beta tester. It's not about getting it perfect, it's about making it work at least fairly reliably. ----- Original Message ----- From: "jim grimsby" <jimgrims@xxxxxxxxxxx> To: <jfw@xxxxxxxxxxxxx> Sent: Thursday, May 06, 2004 4: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