Many times, this shifts burden to users. It's always more convenient to have one API which does exactly what you need.
But the idea here is to keep the API simple and stable in a phase where instability is already high.
Perhaps, after it gets mature, it'll make sense to incorporate common use cases into the API structure for convenience.
Many times, this shifts burden to users. It's always more convenient to have one API which does exactly what you need.
But the idea here is to keep the API simple and stable in a phase where instability is already high.
Perhaps, after it gets mature, it'll make sense to incorporate common use cases into the API structure for convenience.