Re: The answer is not to tell us that buying a new version of JAWS is the proper solution.
To be fair, Microsoft has done exactly the same thing with windows for ages. You install Windows 7 Ultimate from the exact same media as you install Windows 7 home from. The difference is all in the product key. Give it a different product key, the installer turns on the features that key unlocks. This is why you don't need to wipe your system if you're upgrading from home to pro or ultimate. windows 10 very probably works in exactly the same way. I've never been a fan of JFW's licensing system, particularly since they've gotten away from the ability to give back authorization keys you're not using (that's another rant for another thread), but it could always be a lot worse. You pay for a new major version of windows when it comes out, but those usually only come out every couple years - unless MS puts out a complete flop, but come on that never happens. JFW releases a major version of all its software at least once per year, and I get the impression - again, like Microsoft, drops support for previous versions shortly after. Imagine having to pay JFW prices annually?
Before someone jumps on me, I'm not saying this is the right way to do it. we've all given FS/HJ/VFO enough money over the years we've probably earned a long-term support license. HJ had years to do it and didn't. FS had years to do it and didn't. given recent and not-so-recent history, I don't see VFO doing it. I'd love to be wrong, but until I am, I'll just be thankful they're not trying to completely immitate Microsoft. In the meantime, I'm keeping an eye on the current state of Narrator.
From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of Tim Ford
Sent: May-17-17 3:14 AM
Subject: Re: The answer is not to tell us that buying a new version of JAWS is the proper solution.
All good points.
My proposal, boiled down to its essence, is that FS should develop a new version that is back to basics, is as stable, responsive, and functional as can reasonably be done, for the relatively narrow set of tasks that average JAWS users ever do. All the focus of adding complicated new features is fine for the power users, and charging them more seems justifiable.
However, the JAWS “Professional” version is nothing more than activating the components necessary for large office systems, citric, etc. I even learned that the unlocking key is the only difference between the two versions, so FS is selling as a premium pro version a software program that is exactly the same as the less expensive version.
I understand that screen reader software development involves a relatively small target audience, and the profit factor is a major issue. That said, a major re-structuring on how screen readers are developed seems now due.
For us basic users, give us one that does what we need, does it well, and does not suddenly go silent or lock up. Make it available to all those currently using a properly registered copy of JAWS, regardless of how old a version, charge a reasonable one-time fee, and provide a quality overall JAWS experience. For the vast majority of us JAWS users, several generations of JAWS has failed to provide that experience.
I would quit using JAWS right now if it were not for the fact that I hate having to learn a new set of commands. I do only what is or becomes necessary, and I imagine aa lot of us share that attitude.
[mailto:email@example.com] On Behalf Of James Homuth
I guess it depends on whether or not FS/VFO still feels up to supporting older versions of JAWS. I know back when it was Henter Joyce (yeah, I've been around that long), they used to backport potentially major fixes to older JAWS versions. It also depends, I'd imagine, on your definition of an older version. I can see VFO deciding, for instance, okay we'll apply this fix to JAWS 18 and 17, but not 16. And if like me you're still on 14, I can see you being quite reasonably out of luck.
From: firstname.lastname@example.org [mailto:email@example.com] On Behalf Of
I agree. On Outlook 2013 with JAWS 17, new email notifications were not read. With JAWS 18, the email notifications were then read. I feel that an upgrade for that is not fair to the end user as it's not a special innovative feature... Sometimes, I wonder...
On May 16, 2017, at 10:53 PM, Tim Ford <ttford@...> wrote: