←back to thread

263 points itzlambda | 2 comments | | HN request time: 0s | source
Show context
kybernetikos ◴[] No.44608894[source]
The big question for me at the moment is whether to go pay-for-tool or pay-for-model.

If I pay for a tool that includes access to frontier models, then they'll keep the models up to date over time for me, let me use models from multiple providers, and the tool is carefully designed around the capabilities and limitations of the models it works with. On the other hand I can't really use the powerful model the tool works with for other applications or write my own.

If I pay for models, then I can only really use it with that manufacturers tools or tools that aren't optimised for the model but allow you to bring your own keys, and if the model provider I'm paying falls behind then I'm tied in for the duration of the contract. The big advantage is that there is a lot of innovation in tooling happening at the moment and you can avoid being locked out of that or having to pay many times for access to the same frontier models accross multiple different tools.

replies(2): >>44608935 #>>44609040 #
lumost ◴[] No.44608935[source]
I think we'll see a shift to BYO LLM in the future. I saw that overleaf offers an assistant feature and an associated subscription. But I already pay for ChatGPT and Github copilot, I'm not going to pay for a third assistant - particularly when I can just bypass overleaf and use copilot in vscode directly.
replies(2): >>44608973 #>>44609035 #
1. kybernetikos ◴[] No.44608973[source]
I think commercially there'll be a really strong pull for dev tools to resell access to frontier models.

It's hard to make money out of dev tools, but if you tie in a service people are prepared to pay hundreds of dollars a month for, then suddenly it looks easier to make money out of an otherwise unsaleable IDE plugin that accesses that service.

replies(1): >>44609140 #
2. vunderba ◴[] No.44609140[source]
Yeah, Raycast and Warp are two tools that are definitely trying to do this.