4 ms·
> I question this. Each vendor's offering has its own peculiar prompt quirks, does it not? Theoretically, switching RDBMS vendors (say oracle to postgres) was a
by mgh95 1y ago
> I question this. Each vendor's offering has its own peculiar prompt quirks, does it not? Theoretically, switching RDBMS vendors (say oracle to postgres) was also "an afernoon's work" but it never happened. The minutia is sticky with these sort of almost-but-not 'universal' interfaces.
The bigger problem is that there was never a way to move data between oracle->postgres in pure data form (i.e. point pgsql at your oracle folder and it "just works"). Migration is always a pain, and thus there is a substantial degree of stickiness, due to the cost of moving databases both in terms of risk and effort.
In contrast, vendors [1] are literally offering third party LLMS (such as claude) in addition to their own and offering one-click switching. This means users can try and if they desire switch with little friction.
[1] https://blog.jetbrains.com/ai/2025/09/introducing-claude-agent-in-jetbrains-ides/ https://blog.jetbrains.com/ai/2025/09/introducing-claude-age...
- gretch 1y agoThe current LLMs support data export/import inherently because the interface is pure text. All one needs to do is say something like “tell me all of personalization factors you have on me” and then just copy and paste that into the next LLM with “here’s stuff you should know about how to personalize output for me”
- deleted 1y ago[deleted]
- RussianCow 1y agoMoreover, it's trivial to run several LLMs side-by-side for a while and measure the success of each, then migrate to the one that performs the best. And you can even migrate in-progress chats since all the context is passed on each call anyway.