←back to thread

343 points LorenDB | 2 comments | | HN request time: 0.815s | source
Show context
newusertoday ◴[] No.44001807[source]
why does ollama engine has to change to support new models? every time a new model comes ollama has to be upgraded.
replies(1): >>44001834 #
nkwaml ◴[] No.44001834[source]
Because of things like this: https://github.com/ggml-org/llama.cpp/issues/12637

Where "supporting" a model doesn't mean what you think it means for cpp

Between that and the long saga with vision models having only partial support, with a CLI tool, and no llama-server support (they only fixed all that very recently) the fact of the matter is that ollama is moving faster and implementing what people want before lama.cpp now

And it will finally shut down all the people who kept copy pasting the same criticism of ollama "it's just a llama.cpp wrapper why are you not using cpp instead"

replies(2): >>44001901 #>>44002040 #
1. w8nC ◴[] No.44002040[source]
Now it’s just a wrapper around hosted APIs.

Went with my own wrapper around llama.cpp and stable-diffusion.cpp with optional prompting hosted if I don’t like the result so much, but it makes a good start for hosted to improve on.

Also obfuscates any requests sent to hosted, cause why feed them insight to my use case when I just want to double check algorithmic choices of local AI? The ground truth relationship func names and variable names imply is my little secret

replies(1): >>44002065 #
2. Patrick_Devine ◴[] No.44002065[source]
Wait, what hosted APIs is Ollama wrapping?