4 ms·
> you just cargo cult examples from the documentation This mindset, and libraries that are basically only usable in that way if you don't want to invest months
by jules 15y ago
> you just cargo cult examples from the documentation
This mindset, and libraries that are basically only usable in that way if you don't want to invest months of your time are the bane of programming. Library writers, please:
1. Design the API by thinking about how it will be used, not how it will be implemented.
2. Make sure that your publicly exposed interface can be specified simply. If your specification is anywhere near as complex as the code implementing it you know you're doing something wrong; your library is not reducing complexity.
- rubashov 15y agoThe complicated parts of boost where this is what you end up doing are really more like libraries for library writers. You'd almost certainly wrap something like Boost.Geometry for your specific needs. It's made with flexibility as the goal. So it's really not the problem you're presenting. The alternative is dozens of different half-baked libraries for specific use cases.