3 ms·
ROTFL, I had to laugh so hard! "Without the Bloat" vs. "litellm routes LLM calls across providers and translates between message formats. That core is buried
by skrellm 22d ago
ROTFL, I had to laugh so hard!
"Without the Bloat"
vs.
"litellm routes LLM calls across providers and translates between message formats. That core is buried under 100k+ LOC"
Seriously anybody considering 100k+ LOC not a bloat? You made my day!
Let's just say the author's and my definition of bloat is not the same. Full disclosure, I'm the guy who reimplemented etcher (over 400Mb) in a mere 300Kb, Capstone (over 1Mb) in only 66Kb and who compressed LPC charactersheets (over 700Mb) into 4Mb. That's my interpretation of "non-bloated".
- pama 22d agoYou misunderstood. This new project has 2,900 LOC. Maybe the spelling change is too subtle.
- skrellm 22d agoNo, you forgot about the dependencies (others said it to be 700Mb). And 2,900 LOC is still way too much for handling a remote API call, especially in a high level language such as Python where the biggest part of the task is delegated to separate modules. I wrote an entire https client from ground up in 117 LOC (and in a low level language, not Python): https://gitlab.com/bztsrc/skrellm/-/blob/main/src/https.c https://gitlab.com/bztsrc/skrellm/-/blob/main/src/https.c Again, this guy and me disagree on what "not a bloat" means.
- Terretta 21d ago> you forgot about the deps… (… 700Mb) On the contrary, the readme for this project, `litelm`, is contrasting with the bloat project, `litellm`. This project subty deboats an L. The bloat (or featuritis) project has the 700mb and 100k+ LOC, this de-bloat has 2k LOC and specifies its only two deps ones most people want as deps (although httpx should be swapped to its successor). So this response is off base, the 700Mb isn't forgotten, it's been dropped.