The beta testers aren't blind or stupid, the speed issues were initially so bad I had to buy a new computer just to run the betas! Even my newer computer was sluggish until I gave it more RAM and a WD black series hard drive. Others both beta testers and regular users with older slower computers have provided similar feedback.scouseware wrote:Collecting mail off a server is not rocket science and neither is getting a responsive GUI in a reasonably well programmed application. I don't know what you guys are writing but as far as I am concerned questions like "what is slow' in the new mailwasher GUI means to me the testers are either blind or the testing is done on a CRAY supercomputer running windows. Get yourself a low budget / low speed PC and try to get the new version running fast on that. You may find an improvement in customer responses and you may also be able to see the obvious. The new Mailwasher 2010 speed sucks and I feel as though I have wasted a tenner!
You can ask for your money back but I'd sure rather you hang about and continue to complain about speeds with each new release. Maybe they can get closer to the performance we see in v6 (can't get all the way there due to the more complex spam evaluations) if enough folks complain.
yahoobenyahoo That is an excellent issue on the friends list, I don't use it much as I keep getting forged messages that fool it but it is silly to have to sit and wait just to open the tab and fill the list when you wanted to do something else. Part of the delay is that the friends list is stored in the database, not a text file and it is converted to regex code for faster evaluation and to support coming enhancements to reduce the forgery problems and other user requests.
My biggest gripe right now is the filter evaluation speed, get a bunch of complex filters in place and best have a couple minutes if there is much mail coming in. Second in line is the move/mark speed already mentioned, on my system it really got bad after checking a big batch of messages, worse if bolding unread was enabled, that may be fixed in the next release so I'd hang on to see how that goes. I pulled down 40,000 some messages into the latest beta version with good results last night with good results.
The firetrust folks have been working on this program for a long time and there have been a good number of folks beating on the beta code, a huge number of bugs, UI glitches and improvements have been made. They still have a pile of bugs from the beta testers, suggestions for more features and fixes for stuff that is not quite right and just picky stuff like spellink err0rs. Now the users get their say and firetrust can prioritize work based on the complaints they get.