2013/11/5 T. Modes <[email protected]> > Hi Frederic, > > Am Dienstag, 5. November 2013 10:41:19 UTC+1 schrieb Frederic Da Vitoria: > >> OK, I'll refrain from advising this from now on. But you realize that >> similar problems have been going on for several months (more than a year?), >> that it generates frustrated Windows users (I have a hunch this is a >> Windows-specific issue) and that in the Windows world, the general user >> behavior is: "if the software doesn't work, then use another one"? Windows >> users who know what a bug tracker is (I am not even saying "who know how to >> use a bug tracker") are few. So that letting users get hit by PTBatcherGUI >> problems might achieve getting less Hugin users instead of solving the >> PTBatcherGUI issue. >> >> It would be nice if all would always works. > There is always a conflict between adding new features (with maybe new > bugs) and rock-solid stability. If you prefer always rock-solid stability, > we can not add new features, because we have not the man power to test them > before release to this extent. > So in the scope of our little project with hobby people we need the > feedback from the user (with a wide variety of systems and wide variety of > use case, not to mention the big variety of image format..) to fix the > issues and make it more stable. So features can become more stable with > time - but only when they get tested and issues reported and fixed. > > Big software team can do that testing more extensive before release - but > they have the man power, time and money. > > But here it often goes: > 1.) Does not work! > 2.) Try to identify the culprit and give ideas to try. > > And then it ends. No feedback, no this solved it or so. So we can not fix > the issue or make it more robust, because we don't know what goes wrong in > specific conditions. > > To use an overstressed comparison: When you car does not work correctly, > do you then go to the garage and say simply "The car does not work > correctly."? Yes, then you have a very fine garage. But I think in most > case they ask you, what exactly does not work and try to isolate the > failure. > > But here it gets expected that all should work in all user cases on all > machines around the world with all different images, and this in the first > run. >
I understand this; I am a software developer myself. I also agree with the open source way of things, I am not saying the average Windows user is right. But I also know the mentality of the average Windows user. After all, Microsoft does not precisely sell Windows as a collaborative OS where each user can help improving it's features :-) So it should be no surprise that Windows users are this way statistically. -- Frederic Da Vitoria (davitof) Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/CANe_y9TWyFa%3D9%3DhOX47dn22TpSxwfgMOSD8NUqK7%2BrS%2BJ7YXwA%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
