Hmm...maybe it should be repackaged into a Saas product with a monthly, per user license!
And a cookie notification.
Re:Things to Know About GNU Readline
by DoofusOfDeath on Thursday August 22, 2019 @07:30PM
(#20773332)
Maintained by a single person, but I doubt that individual is irreplaceable as maintainer.
One reason we get so much bang-for-the-buck with software is that the maintenance costs for a given software package aren't necessarily proportional to the number of places/times it gets used.
Nobody is irreplaceable.
He maintains bash too!
How many people does it need maintaining it? It's not that big, and there isn't that much that needs change.
> It's not that big, and there isn't that much that needs change.
Not... That... Big? It is a _huge_ library. A naive wc -l of just the c files, and none of the headers, lists a result of 30,654.
That's not a small project. And as it's a library and not a self-contained application, that's one of the bigger libraries around. In fact that's one of the sighted inspirations for linenoise, that readline is too big.
Re:Things to Know About GNU Readline
by longcommonname on Saturday August 24, 2019 @11:01AM
(#20787482)
30k lines is not huge, large or big. It's medium size.
Let that sink in. How many developers and admins rely on readline for their daily work? How many critical installations world wide depend on it?
As a contrast: How much revenue is generated with, and how many people work on, something as mundane as a chat application for mobile phones?
Sometimes it is astonishing that our software eco system actually works.