May 31, 2026 · 28 min · 12 segments
What makes a good library? Support us on Patreon and get an ad-free RSS feed with early episodes sometimes See our contact page for ways to get in touch. Subscribe to…
No entities detected.
I think it's a really interesting question.
I think that there's a real big difference between using some libraries and using some other libraries, and sometimes there's a difference between a framework and a library.
But I wonder, Kevin, when you were designing Clap, did you have in your mind, like, principal ideas about what a library should be like, or were you just sort of going with the flow?
If we go back to the very beginning, no.
Uh, the very beginning was, like, 2013, 2014, probably somewhere in that timeframe, and I originally wrote that actually just as, one, an excuse to learn Rust and, two, because the place that I was working at the time, we had a bunch of, like, small command line utilities and little things that we had to run, and I wanted to use Rust for those.
But we had to mimic certain CLI patterns or whatever from, from other things.
So I thought it was kind of a good idea to, like, build a library that I could use that would also help teach me Rust.
So that was the original intent.
However, fast-forward, and I learned very quickly, like, there, there's a lot of things to consider when you're making a library for public consumption, and a lot of things I did wrong at first, or things that, like, didn't really matter to me at first, and I found better ways to do them.
So, uh, you know, this is 2014 timeframe.
We're talking 12 years ago.
There's a lot that's changed since then, and, you know, I've learned a whole lot on how to make libraries.
But I would say the, the number one thing, though, is, like, what is it that actually matters about your library? Because when we say, like, what makes a good library, there's all kinds of different scales of good.
There's, "I just need it to work." There's, "I need it to be performant." There's, "I need it to be secure." There's, "I need it to be, like, pleasant to use or have a good intuitive API surface for users." There's all kinds of different metrics that we could say, like, "Is this library good on?" And some of them are opposing.
So I would say number one thing is, like, figure out what you mean by good and which ones you want to prioritize or at least prioritize first.
Yeah.
I think it's a really interesting question.
I think that there's a real big difference between using some libraries and using some other libraries, and sometimes there's a difference between a framework and a library.
But I wonder, Kevin, when you were designing Clap, did you have in your mind, like, principal ideas about what a library should be like, or were you just sort of going with the flow?
If we go back to the very beginning, no.
Uh, the very beginning was, like, 2013, 2014, probably somewhere in that timeframe, and I originally wrote that actually just as, one, an excuse to learn Rust and, two, because the place that I was working at the time, we had a bunch of, like, small command line utilities and little things that we had to run, and I wanted to use Rust for those.
But we had to mimic certain CLI patterns or whatever from, from other things.
So I thought it was kind of a good idea to, like, build a library that I could use that would also help teach me Rust.
So that was the original intent.
However, fast-forward, and I learned very quickly, like, there, there's a lot of things to consider when you're making a library for public consumption, and a lot of things I did wrong at first, or things that, like, didn't really matter to me at first, and I found better ways to do them.
So, uh, you know, this is 2014 timeframe.
We're talking 12 years ago.
There's a lot that's changed since then, and, you know, I've learned a whole lot on how to make libraries.
But I would say the, the number one thing, though, is, like, what is it that actually matters about your library? Because when we say, like, what makes a good library, there's all kinds of different scales of good.
There's, "I just need it to work." There's, "I need it to be performant." There's, "I need it to be secure." There's, "I need it to be, like, pleasant to use or have a good intuitive API surface for users." There's all kinds of different metrics that we could say, like, "Is this library good on?" And some of them are opposing.
So I would say number one thing is, like, figure out what you mean by good and which ones you want to prioritize or at least prioritize first.
Yeah.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.