3 ms·
> So, to say, I usually pick Quality and Velocity. Velocity is what you choose when you have a runway. The most successful open source projects like Emacs and
by jart 3y ago
> So, to say, I usually pick Quality and Velocity.
Velocity is what you choose when you have a runway. The most successful open source projects like Emacs and GNU Make have been sitting around for about 40 years now, being slowly and steadily maintained by their owners. I've been working on a C library of my own for the past 6 years and it's only started to gain traction in recent months. If I was doing it as a startup my project would have been laid to rest in a charnel house long ago. But since it's open source, the only thing it's really cost me is time.
- zarathustreal 3y agoIdk which project you’re talking about but thank you again for your work on the various APE, Redbean, etc!
- marc_abonce 3y agoI'm also wondering to what extent does the stack or framework force you into prioritizing velocity. For example, I've never worked with Vue but if it's anything like React, I can imagine that a library could quickly become "outdated" after a year or so unless you constantly keep the dependencies up to date and maybe even change any dependency that becomes deprecated.
- deleted 3y ago[deleted]