Software Architecture: What is a good library?
In my last post I told you something about parallel libraries. I will talk about some of these in further posts. First at all I have to define: What is a good library for me? There are several metrics for a good library. Here are mine:
- Stable, library doesn’t crash the application
- Easy to use, simple API
- High performance (speed, memory consumption)
- High Portability
- Further support
A library should not cover all the problems in software development. I prefer to use more good libraries than one giant library. A library is a piece of code that is very specialist. Library developers should be aware of, that their library would be in use over the next 10 years. Developing a library sounds very easy. But developing a simple library that covers the most problems, for which the library is created for, is one of the hardest jobs in software development. I will show you some examples, which show both sides (good and bad) in further posts here.
So long, stay tuned