Live data from Hacker News

The local LLM ecosystem doesn’t need Ollama

sleepingrobots.com

41–50 of 222 posts

Re: The local LLM ecosystem doesn’t need Ollama

#41
post #16

It feels like a bit of history is missing... If ollama was founded 3 years before llama.cpp was released, what engine did they use then? When did they transition?

They spent several years in stealth mode but the initial release was llama.cpp.

Ollama v0.0.1 "Fast inference server written in Go, powered by llama.cpp" https://github.com/ollama/ollama/tree/v0.0.1

Re: The local LLM ecosystem doesn’t need Ollama

#42
post #16

It feels like a bit of history is missing... If ollama was founded 3 years before llama.cpp was released, what engine did they use then? When did they transition?

I don't think that is the case. Llama.cpp appeared within weeks after meta released llama to select researchers (which then made it out to the public). 3 years before that nobody knew of the name llama. I'm sure that llama.cpp existed first

Re: The local LLM ecosystem doesn’t need Ollama

#44

Earlier quoted context omitted.

> This creates a recurring pattern on r/LocalLLaMA: new model launches, people try it through Ollama, it’s broken or slow or has botched chat templates, and the model gets blamed instead of the runtime. Seems like maybe, at least some of the time, you’re being underwhelmed my ollama not the model. The better performance point alone seems worth switching away

I follow the llama.cpp runtime improvements and it’s also true for this project. They may rush a bit less but you also have to wait for a few days after a model release to get a working runtime with most features.

Model authors are welcome to add support to llama.cpp before release like IBM did for granite 4 https://github.com/ggml-org/llama.cpp/pull/13550

Re: The local LLM ecosystem doesn’t need Ollama

#45

For most users that wanted to run LLM locally, ollama solved the UX problem. One command, and you are running the models even with the rocm drivers without knowing. If llama provides such UX, they failed terrible at communicating that. Starting with the name. Llama.cpp: that's a cpp library! Ollama is the wrapper. That's the mental model. I don't want to build my own program! I just want to have fun :-P

but if ollama is much slower, that's cutting on your fun and you'll be having better fun with a faster GUI

Re: The local LLM ecosystem doesn’t need Ollama

#48

No mention of the fact that Ollama is about 1000x easier to use. Llama.cpp is a great project, but it's also one of the least user friendly pieces of software I've used. I don't think anyone in the project cares about normal users. I started with Ollama, and it was great. But I moved to llama.cpp to have more up-to-date fixes. I still use Ollama to pull and list my models because it's so easy. I then built my own set…

I spend like 2 hours trying to get vulkan acceleration working with ollama, no luck (half models are not supported and crash it). With llama.cpp podman container starts and works in 5 minutes.

Re: The local LLM ecosystem doesn’t need Ollama

#49

Earlier quoted context omitted.

Llama.cpp now has a gui installed by default. It previously lacked this. Times have changed.

While that might be true, for as long as its name is “.cpp”, people are going to think it’s a C++ library and avoid it.

It would make sense to just make the GUI a separate project, they could call it llama.gui.

Re: The local LLM ecosystem doesn’t need Ollama

#50

Earlier quoted context omitted.

Llama.cpp now has a gui installed by default. It previously lacked this. Times have changed.

While that might be true, for as long as its name is “.cpp”, people are going to think it’s a C++ library and avoid it.

This is the first I'm learning that it isn't just a C++ library.

In fact the first line of the wikipedia article is:

> llama.cpp is an open source software library

Post reply on HN