|
If you can't make a program to work your way, it means it doesn't work at all. That include how does it look and what features will it have. Everyone must have an opportunity to write feature, even most "simple users" will just use features, not write them.
So what you need is:
How to write a tool?
How to remove a tool?
|
|
|
|
|
Stability is the most important quality.
Many components look nice but when starting to play with some become unstable which points out to the "matureness" of the product.
In small software pieces this isn't so important but in enterprise software stability is a must.
Also, the average time it takes for the support team to fix a bug or add a simple feature.
|
|
|
|
|
Gilad Kapelushnik wrote: Also, the average time it takes for the support team to fix a bug or add a simple feature.
And in that process they should ensure that it does not break any earlier fixes or introduce more bugs.
Vasudevan Deepak Kumar
Personal Homepage Tech Gossips
The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep!
|
|
|
|
|
The biggest question for me: will this component become a deadweight in the future?
That means either a reputable owner who can be expected to still exist and maintain this product in five years or a good customer base so I can expect that even if the vendor goes down someone else will pick up and continue the product or source code.
Now, source code seems to be the most reliable answer. However, this makes modifying the lib tempting - which in turn makes upgrading a pain.
Personally, I love the idea that Raymond spends his nights posting bad regexs to mailing lists under the pseudonym of Jane Smith. He'd be like a super hero, only more nerdy and less useful. [Trevel] | FoldWithUs! | sighist
|
|
|
|
|
I agree, whether the company will die, or new version does not compatible with old version
Regards,
unruledboy_at_gmail_dot_com
http://www.xnlab.com
|
|
|
|
|
For a small feature that I myself could write in say a couple of hours but lack the time to do so due to an approaching deadline, I'd happily pay 10-25 bucks since it's cheaper to buy it.
For a very complex, feature filled library (example the Dundas stuff, DevEx etc.), that saves me days and days of work, effort, testing... I'd be willing to pay much more.
|
|
|
|
|
Usually I mix price, features, testimonials and trial version in my decision making process; I don't chose things only for one reason, never.
Sometimes my filter is much more definite than one I mentioned above.
|
|
|
|
|
|
|
Yep, certainly a new low.
|
|
|
|
|
What is the MOST important?
|
|
|
|
|
well it's hard to say : what do you prefer : living with 15 meters arms or with a Calf head ?...
|
|
|
|
|
|
^^
of course my example was bad, but i think you got it
|
|
|
|
|
How about a combination of them? Things are not black and white in this life
|
|
|
|
|
nuff said
"I beseech you, in the bowels of Christ, think it possible you may be mistaken." -- Oliver Cromwell
|
|
|
|