Re:RubyLLM: A Ruby framework for all major AI providers
by piratebroadcast on Wednesday June 24, 2026 @04:26PM
(#48665201)
Why build it in such a way that there you're locked into one provider when you can just use this tool and have the ability to choose any provider in the future? I mean, even for fallbacks, like what if anthropic API is down that particular day when you need the service?
[ Parent
| on HN ]
Re:RubyLLM: A Ruby framework for all major AI providers
by hakunin on Wednesday June 24, 2026 @05:07PM
(#48665646)
Not the commenter, but the reason is the same as the choice to use direct db driver vs ORM - you get to take full advantage of special features and intricacies of one system, rather than trying to maintain a lowest common denominator of functionality between multiple ones.
You can always build multiple clients however. It could be one thorough integration with one API, and a simpler backup via RubyLLM.
Unless of course RubyLLM supports all of the above, but even then, are they going to be able to keep up as much as a native client in the long term?
The answer is almost always that a native client for a more critical integration is the right call. You can always add another if you need it.