Re:Annoyances of API Design
by euske on Thursday January 28, 2016 @09:51PM
(#10993180)
API naming is hard because of the conflicting goals:
1. You want to make it easy to type/read.
2. You want to make it descriptive. (conflicting with #1)
3. You want to make it consistent and unique.
4. You want to make it compatible with older APIs. (conflicting with #3)
5. You want to make it unambiguous.
6. You want to make it flexible/amenable to future changes. (conflicting with #5)
...
etc, etc. It's just impossible to meet all these requirements with developers that live in a different time and space.
1. You want to make it easy to type/read. 2. You want to make it descriptive. (conflicting with #1) 3. You want to make it consistent and unique. 4. You want to make it compatible with older APIs. (conflicting with #3) 5. You want to make it unambiguous. 6. You want to make it flexible/amenable to future changes. (conflicting with #5) ...
etc, etc. It's just impossible to meet all these requirements with developers that live in a different time and space.