amos“every rust project has a billion dependencies”
oh no they made code composable oh nooooooo should we call someone??
rust has a lot of problems, but let me tell you: “micro libraries” isn’t one
splitting packages per concern is good for build performance, it’s good for review, it’s good for API evolution.
the problems are technical (compiler perf), financial (funding OSS), human etc.
Simon Richter@fasterthanlime the problem is that micro libraries have their interface derived from the implementation, and similar problems require a different micro library with a similar but subtly different interface, and neither of these is maintained going forth because they are feature complete as defined by their interfaces.
Dark@GyrosGeier @fasterthanlime code shouldn't have to be endlessly maintained
we should be able to call a project done rather than abandoned
we should be able to call a project done rather than abandoned
@dark @fasterthanlime yes, but that requires a definition of "done" that is not attached to the first (and, in the beginning, only) dependent project, and it requires the interface to be designed around anticipated future needs and in a way that will allow dropping in later versions.