I also was considering it, but when I see how much some stuff are getting fucked out, I am  holding it till it will be fixed.

Hi,
Good on you, hurstseth405.
I really really want to donate to NVDA too, as its the sort of project that relys upon its users for donations and survival and considering how useful it is and that its able to hold its own against payed screenreaders jaws etc, that in my opinion is worth monthly donations or whatever whoever is able to contribute.
But my financial situation doesn't allow me to do so.
Grryf

Since myself and my wife both use NVDA on a very regular basis, I felt it was only fare to donate. I am on the monthly subscription system, donating 10 australian dollars a month, which is just over six  pounds in the Uk.

I wanted to give monthly donations since I'd obviously like to keep the ongoing development of NVDA running, and all in all 72 quid a year is still slightly less than the 200 or so every 18 months I would've had to pay for new supernova upgrades.

I can't say we're doing so well financially at the moment, but giving monthly donations did seem only fair.
The only thing I do wish is that NVDA would stop with the nag boxes when I'm already donating to them everytime I install a new version .

Well, I stopped donating when I really had to cut costs, and never restarted, Now I will not restart because it's gone downhill so dramatically I will not help fund the project to it's doom.

I was considering donating to NvDA but never did. Now, I'm not even sure I will. I've lost faith in the development team of NvDA. They have over 2000 open issues (which is ridiculous) and still haven't found a way of solving it, and whenever I bring up something like 64-bit builds (which is becoming more and more necessary as time goes by) they stonewall me at every turn, coming up with excuses that make absolutely no sense at all. I've tried platitudes, I've tried being kind. I've stated the advantages and the reasons for why they should do it but no, they won't, because "oh, its too difficult", despite that they already have the framework there and practically every other screen reader has done it. It doesn't help that I've heard roomers of performance issues and bottlenecks, and I've suffered periods where it will freeze for about 5-10 seconds and then come back, and NVAccess still hasn't solved those problems. I know, this sounds like a rant, and  apologize but I needed to say it.

@11, I know. And its complete lunacy. I have o doubt that if NVDA was 64-bit we'd see a huge performance boost purely because NVDA would have full access to the systems resources. I serously wonder if any of them have even tried... if their saying that it has no performance benefit than clearly not. Sad, that...

@13, exactly. They can weather the storm themselves. If they won't even consider 64-bit then their not worth my time, because 32-bit is dying, slowly but surely. Its already been tortured to death in the TCP/IP world with IPv4 and its been almost eliminated completely in the world of computers. Honestly I'd love for the entire team to just be completely overthrown and replaced with a team that *actually listen to the community*.

I also do not understand what exact reason is behind to believe that 64-bit support would increase NVDA's performance. I guess the freezes that NVDA sometimes causes comes from window message handling and temporary / permanent deadlocks. 32-bit (WOW64) simulation doesn't slow down much. And as the member said, SSE2 is not something boosts any kind of program, the way he / she expressed was obviously harsh though.
Of course I could be wrong; there might be some definitive reasons. This is not something to try to counter-argue against people who want 64-bit transition.

@15, OMG just wow. That kind of attitude from those kinds of members -- not you but the member who replied to you -- is what makes the NVDA mailing lists so toxic. By that members own logic, JAWS shouldn't have switched to 64-bit. So I wonder why they did? After all, he did say that there's supposedly no performance benefit. Yet FS did it anyway... doesn't that, you know, defy his statement? I mean, if I'm not mistaken JAWS got faster with the 64-bit versions but released 32-bit versions too. (Someone should probably test this, since I most likely won't.)
@17, really? I'd love to know *which* braille display drivers don't support 64-bit, because I can't think of any off the top of my head. I'm not intimately familiar with braille drivers, but I'd think that most of them would've switched to 64-bit purely because JAWS supports most braille displays out there.
Either way we've seriously hijacked this thread.

@19, yep, I am, but they never gave me anything about braille drivers not being available in 64-bit builds at all. They have 32-bit build of liblouis, but that's available in 64-bit too.
I am also curious if said member has even ever tried a 64-bit build of NVDA and benchmarked them. Granted, benchmarks aren't very reliable, but if he can prove that there is absolutely no performance benefit whatsoever to using a 64-bit build of NVDA, then that will be that. But so far they seem overly-confrentational and know-it-all-ish and (IMO) they should be removed purely because of their toxicity. On a mailing list, that's not very productive. A forum can handle it but a mailing list usually can't. "Trying to spread the panic," eh? In what way? I haven't seen this "panic" he speaks of... I mean, since this subject was brought up I haven't seen anyone panicking. I've seen calm discussion of a subject that has no sense of panic in any way, on this topic anyway.

@21, I have expressed my reasons for not having much respect for the team. The people on it have good intentions, but ever since Jamy left (I hope I spelled his name right) NVDA has been declining badly, and the reports I've heard from others about performance bottlenecks, outright freezes, and so on still haven't been fixed. I myself have even experienced a common symptom where NvDA will receive a huge chunk of text and outright stop responding. Then it will start speaking, and most o the time I have to restart it to get it to shut up. And that's not all, I'm sure you (along with many others) have experienced these issues, and so far I've seen no initiative from the developers to fix them. The developers failing, IMO, is allowing themselves to be swamped in issues and problems with NVDA. The documentation of the codebase is poor (I'd even go as far to say that the documentation is practically nonexistent), and so these issues have piled up and piled up and, while they've fixed some of them, there are still 2,000 plus that are still open, some open from 2008. 64-bit is dying very slowly i nthe Windows world, I'll give you that. In the Mac world its already dead, and in Linux its as much as dead. Most of the "regular Linux distributions" (i.e. Arch Linux) no longer even support 32-bit. Ubuntu no longer gives out 32-bit desktop images. Tails OS, elementary OS, Solus... none of these support 32-bit versions. Here's the thing: Microsoft still supports 32-bit because of all the old apps that are still used to this day, and they probably have other reasons too that I'm not aware of. But, like Apple, they could very, very easily remove your ability to use 32-bit apps -- and it would most likely require one update. Only one. Granted, the likelihood of them doing that within the next month, year, or hell, even decade, is low. But it is there nonetheless.

Sure thing, MS can do it, you are definitely right, however it wont be sudden and out of nowhere. This is why you have insider builds nowadays, so people can prepare their apps before something like that goes public. Other operating systems are surely different, especially Apple, not as much in the Linux world so can't comment too much. Honestly though, Jamie leaving does not have much to do with this. Technically, he did not even leave, he just officially does not longer work at NV access. He's still active at helping them, as you probably see yourself on GitHub. Hell, even if let's say NVDA was all buggy for a few versions, this cannot destroy the respect they had for such a long time. If it does for people, then that's called disrespectful and ungrateful. I will say that I have experienced some things you mention on here, however for me personally screen reader restarting every once in a while is normal. I'd have even more performance issues if I was to switch to Jaws. I do understand each user feeling frustrated about this, however it does not just change in one version. Such things as you probably understand yourself need debugging, and most importantly need time to work on. But let me ask this: They themselves use NVDA as their primary screen reader, and a way to access their computers. So, would you think they would give us a broken product and not do anything they can to improve it? Performance issues hurt them as much as they hurt us, but sometimes there are external factors involved with this that could just be out of their control. It can be UIA doing something bad and freezing NVDA, or just some weird bug Microsoft does not get around to fixing. Really the whole NVDA is dying thing needs to calm down. I'm curious about these open issues though. I don't think so many can be relevant nowadays, and thinking that in 2008 NV access didn't even use GitHub but just used their own servers, perhaps while moving those something went wrong and they remained open? Most issues nowadays are closed as soon as a fix is available, however before this was not such a common practice.