Big-Jim wrote:Did anybody actually read what I wrote?
I did, including the childish shot about me being wrong. (I actually thought of saying that, too, but was the "bigger" man, I guess
Plus, you didn't even say what
was wrong. Was I wrong by saying that lower cost was an advantage if all products did what you need? Or was I wrong by saying that cost is often a
determining factor? Unless you can show how one of those statements was incorrect, then I wasn't wrong (at least not this
Look, everyone is entitled to their opinion, so you can voice whatever you feel is right.
I did, but you still said that I was wrong.
But the thing is, when you want to use a piece of software, you want the software to do what you need it to do. My whole point is this, if you settle for software that does NOT do what you need it to do, just because it is free, you will not be happy with it.
Now who's not reading? I didn't say that people were using phpBB "just because it is free". I suspect many people are using it because it's "good enough" and
Consider a pathological case. Software A does 95% of what you need and costs $100 (an amount that fits in your budget). Software B, the only competitor, does 100% of what you need, but costs $100,000 (which is WAY outside of your budget). Do you:
1) Go with Software A and trim your requirements?
2) Take out a second mortgage on your house to get Software B?
3) Scrap the project entirely because you won't be "happy" with Software A and can't afford Software B?
I think that many people would choose option 1. If you do, too, then cost was one
of the determining factors (the other was that Software A was "good enough", albeit not perfect). If you wouldn't choose option 1, maybe you don't see shades of gray, only black and white.
You can argue that the extra 5% weren't really "needs" then, but were "wants". However, oftentimes it's those "wants" that are what make us happiest, not the "needs". I don't "need" a Porsche that goes 195 mph, but I'd be really happy if I had one.
Or perhaps there's a workaround that lets you do the job with Software A. Suppose that the feature that Software A was missing was the ability to automatically create end-of-month activity reports. Maybe I could write a CRON script that ran and generated those reports instead. It wouldn't be Software A doing it, but that might be good enough. Worst case, maybe you set a reminder in Outlook to run Software A's reporting module every month. You might not be "happy" doing that, but you might be happier than spending $99,900 more or not doing the job at all.
Nobody is ever happy about compromises, but most of us have to make them in many
parts of lives. Software is often just one of those things.