December 9, 2022
Before a dissertation on Designing Go Libraries, Abhinav Gupta essentially tries to talk you out of it:
Do you need to write it?
Owning and maintaining a library can be a significant undertaking. The work does not end once the code is written—there is often a never-ending stream of bug fixes, feature requests, new use cases, and integration work that needs to be done. This is true even for libraries that are only used internally within a company. In fact, the more popular and actively used a library is, the more new work it is likely to generate. Maintaining a library is a continuous process, and it’s never truly “done” as long as it’s in production.
Therefore, before embarking on the journey of writing and maintaining your own library, consider whether there are existing open source alternatives that could meet your needs.
Nothing new here, just a classic example of the push/pull of open source. We all benefit so (so so) much from open source, yet participating in it is essentially punishment.
I’ve just spent nearly a month on one of those, as Gupta says “libraries that are only used internally within a company”, thinking hmmm maybe this is a nice thing to open source, but then reality clicks in and I’m like nah I absolutely do not have the spoons for that.
Related
🤘
ncG1vNJzZmibmKe2tK%2FOsqCeql6jsrV7kWlpa2dhZ3xxhY6mpqudXaG2rLGMp6apnZ5iwLDB0ZycaA%3D%3D