How then can we effectively gauge what tools have a better chance of weathering long-term growth spurts and monetary crunches? Does anyone know of a good assessment rubric/checklist/worksheet out there for this? What factors should be considered before adopting a 2.0 tool? Are there factors to weigh that are different, for example, from assessing a product or hardware package?
Things that come to my mind, but I'm sure I'm missing a ton of considerations (it's Friday afternoon, so my mind is mushy!):
- weighing development/adoption time against record of stability (in other words, if it's a smaller-scale project, you might be able to chance using a tool that is less time/stablity-tested).
- look at creator/company specifics and mission plan
- look for reviews of tool
- inquire about server specs and biz plan for growth
- look at stability of other products, if any, of developers