Comment Tracking the Scene (Score 1) 227
Part of picking libraries/frameworks is staying up-to-date on how things change over time in the community for that language/platform. Getting a feel for the trends and how the current trends compare to previous ones will help you make this decision.
Side Note
Keeping the important/abstract business and data logic modular should reduce the impact of choosing something that dies later on. In the Java realm (just for example), there are frameworks that do their best to keep your code in Plain Old Java Objects, keeping your code relatively "vendor-clean". Using interfaces judiciously could be your savior later on.
Related Questions
Side Note
Keeping the important/abstract business and data logic modular should reduce the impact of choosing something that dies later on. In the Java realm (just for example), there are frameworks that do their best to keep your code in Plain Old Java Objects, keeping your code relatively "vendor-clean". Using interfaces judiciously could be your savior later on.
Related Questions
- Is it backed by a recognizable/reputable company?
- Is anything good written in it that you've used?
- Is there paid support? Not that you'll use it, but are there humans somewhere that will claim responsibility for this product?
