I have a feeling that these discussions occur after every release. These problems could be solved by dropping the new system and going back to the old.
I do not think RB does an adequate job of balancing adding new features, fixing preexisting bugs as well as eliminating bugs that are introduced by the addition of new features. This would seem to be an extremely demanding situation for their programmers. Supposedly they are using the same versions of RB that we are to build the newer versions. This might help, but there seem to be a lot of very obvious and very basic bugs that get through to meet deadlines. This philosophy really doesn't seem to work for them and I doubt that it does for most software companies that offer complicated applications or those that don't have very large staffs. It seems to be a vicious, spinning circle where they have to toss on ideas and hope they stick well enough, while also trying to fix some of the dangling problems as circle continues to spin and spin... I used to be indiscriminately pissed at RB, but now I think I've moved on to pitying their programmers...and feeling kind of sad at the whole situation. I really like RB, but I have a feeling that if they don't get their act together, they're going to crash. I want software that works correctly, not speed of light, mandatory, under-tested, buggy quarter-year releases. With all that said, I still have hope that they really are using the same software to design and that this will make a (huge) difference. _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
