This really demonstrates the utility of pulling in a library written by experts in the field the library handles.
replyThis is a problem I have a lot in modern programming ecosystems: How do I tell the difference between a library written by a team of experts who have spent decades optimizing everything to do with the task and a library written by one guy that's an unnecessary straightforward wrapper over the obvious implementation?
reply1. Read the code
2. Don't. Encapsulate and put yourself in a position to swap out the implementation at will.
reply(Maybe you'll swap out an unnecessary dependency for a simple helper function of your own).
Or increasingly, a library written by an LLM referencing a pile of such “one guy” projects of varying levels of suck (from actually good to good-got-it-is-full-of-suck).
replyWhat I have been seeing recently is having a great LLM rewrite the library leads to fewer bugs and also optimized for your use case. More expensive for sure than pulling something like epub.js but when the library has infinite open issues it can be a lot better.
replyYou defer to the advice of experts you trust. Which somehow have become harder to come by in terms of signal to noise than 20-30 years ago.
replydeleted
reply