I wrote an article on API design way back in 2008 that advocated for "Scaleable" APIs, in terms of user-investment, which dovetails exactly w/ this concept of "Laddering" APIs:
> With this layered approach to File I/O, GScript users do not need to become familiar with the complicated Java I/O libraries to do simple and even moderately complicated things. Yes, there is now some redundancy, but each layer fulfills a particular band of the complexity/performance continuum. GScript programmers are only required to know as much about I/O as is necessary to solve the problem they have with acceptable performance.
I wrote an article on API design way back in 2008 that advocated for "Scaleable" APIs, in terms of user-investment, which dovetails exactly w/ this concept of "Laddering" APIs:
> With this layered approach to File I/O, GScript users do not need to become familiar with the complicated Java I/O libraries to do simple and even moderately complicated things. Yes, there is now some redundancy, but each layer fulfills a particular band of the complexity/performance continuum. GScript programmers are only required to know as much about I/O as is necessary to solve the problem they have with acceptable performance.
https://guidewiredevelopment.wordpress.com/2008/10/05/api-de...