Live data from Hacker News

Ollama's new app

ollama.com

271–280 of 299 posts

Re: Ollama's new app

#271
post #188

I don't understand this move. A frontend desktop application is the opposite of what I and anyone else I know uses Ollama for. It's a local LLM backend. It's been around long enough now that any long term users have found, created and/or adjusted to their own front end interface. I'm comfy, but some of the cutting edge local LLMs have been a little bit slow to be available recently, maybe this frontend focus is why.…

There are many GUIs for Ollama. This looks like a version of Ollama that bundles one.

I agree.

I just can't see a user-focused benefit for a backend service provider to start building and bundling their own frontend when there's already a bunch of widely used frontends available.

Re: Ollama's new app

#272

Earlier quoted context omitted.

I am guessing that the Linux version was first (or the announcement was worded strangely), as it is available on their download page: https://ollama.com/download

thats just the cli versions. this app got gui.

Ah, I missed that detail, thank you for clarifying.

Re: Ollama's new app

#273

Earlier quoted context omitted.

Congratulations on launching the front-end, but I don't see how it can be made for developers and not have a Linux version.

Whoah, are you telling me that there are devs on Linux who use anything else than a tiled WM? CLI or GTFO /s

[deleted]

Re: Ollama's new app

#274
post #91

I gave the Ollama UI a try on Windows after using the CLI service for a while. - I like the simplicity. This would be perfect for setting up a non-technical friend or family member with a local LLM with just a couple clicks - Multimodal and Markdown support works as expected - The model dropdown shows both your local models and other popular models available in the registry I could see using this over Open WebUI for…

Small update: thinking models also work well. I like that it shows the thinking stream in a fainter style while it generates, then hides it to show the final output when it's ready. The thinking output is still available with a click.

Another commenter mentioned not being able to point the new UI to a remote Ollama instance - I agree, that would be super handy for running the UI on a slow machine but inferring on something more powerful.

Re: Ollama's new app

#275

And why should anyone use it or ollama itself?

ollama is probably the easiest tool to use if you want to experiment with LLMs locally.

I literally just turned a fifteen year old MacPro5,1 into an Ollama terminal, using an ancient AMD VEGA56 GPU running Ubuntu 22... and it actually responds faster than I can type (which surprised me considering the age of this machine).

No former Linux experience, beyond basic Mac OS Terminal commands. Surprisingly simple setup... and I used an online LLM to hold my hand as we walked through the installation / setup. If I wanted to call the CLI, I'd have to ask an online LLM what that code even is (something something ollama3.2).

>ollama is probably the easiest tool ... to experiment with LLMs locally.

Seems quite simple so far. If I can do it (blue collar electrician with no programming experience) than so can you.

Re: Ollama's new app

#276

does anyone have a suggestion on running LLMs locally on a windows PC and then accessing them (thru an app / gui) on mac? My windows PC is a gaming PC with a pretty good GPU and I'd like to take advantage of that.

Start llamacpp server with the gui accessible to your Mac?

Re: Ollama's new app

#277

Heads up, there’s a fair bit of pushback (justified or not) on r/LocalLLaMA about Ollama’s tactics: Vendor lock-in: AFAIK it now uses a proprietary llama.cpp fork and builts its own registry on ollama.com in a kind of docker way (I heard docker ppl are actually behind ollama) and it's a bit difficult to reuse model binaries with other inference engines due to their use of hashed filenames on disk etc. Closed-source t…

And llamacpp has a gui out of the box that’s decent.

Re: Ollama's new app

#278

Earlier quoted context omitted.

But it seems like the GUI already connects over the network, no? In that case, why do you need to do user research for adding what is basically a command line option, at its simplest? It would probably take less time to add that than to write the comment.

They will have to support auth if they are adding support for connecting with remote host. It's not difficult but it's not as trivial as you suggested.

Ollama server already supports authentication, and URLs already have a place for credentials.

Re: Ollama's new app

#279

Heads up, there’s a fair bit of pushback (justified or not) on r/LocalLLaMA about Ollama’s tactics: Vendor lock-in: AFAIK it now uses a proprietary llama.cpp fork and builts its own registry on ollama.com in a kind of docker way (I heard docker ppl are actually behind ollama) and it's a bit difficult to reuse model binaries with other inference engines due to their use of hashed filenames on disk etc. Closed-source t…

“Justified or not” — is certainly a useful caveat when giving the same credit to a few people who complain loudly with mostly unauthentic complaints.

> Vendor lock-in

That is, probably the most ridiculous of the statements. Ollama is open source, llama.cpp is open source, llamafiles are zip files that contain quantized versions of models openly available to be run with numerous other providers. Their llama.cpp changes are primarily for performance and compatibility. Yes, they run a registry on ollama.com for pre-packed, pre-quantized versions of models that are, again, openly available.

> Closed-source tweaks

Oh so many things wrong in a short sentence. Llama.cpp is MIT licensed, not GPL license. A proprietary fork is perfectly legitimate use. Also.. “proprietary“? The source code is literally available, including the patches, on GitHub in ollama/ollama project, in the “llama” folder with a patch file as recent as yesterday?

> Mixed Performance

Yes, almost anything suffers degraded performance when the goal is usability instead of performance. It is why people use C# instead of Assembly or punch cards. Performance isn’t the only metric, which makes this a useless point.

> Opaque model name

Sure, their official models have some ambiguities sometimes. I don’t know know that is the “problem” that people make it out to be when ollama is designed for average people to run models, and so a decision like “ollama run qwen3” not being the absolutely maximum best option possible rather than the option most people can run makes sense. Do really think it is advantageous or user friendly, when Tommy wants to try out “Deepseek-r1” on his potato laptop that a 671b parameter model too large to fit on almost anything consumer computer is the right choice and that it is instead meant as a “deception”? That seems…disingenuous. Not to mention, they are clearly listed as such on ollama.com, where in black and white it says the deep seek-r1 by default refers with the qwen model, and that the full model is available as deep seek-r1:671b

> Context Window

Probably the only fair and legitimate criticism of your entire comment.

I’m not an ollama defender or champion, couldn’t care about the company, and I barely use ollama (mostly just to run qwen3-8b for embedding). It really is just that most of these complaints you’re sharing from others seem to have TikTok-level fact checking.

Re: Ollama's new app

#280
post #47
post #38

I've been on something of a quest to find a really good chat interface for LLMs. Most import feature for me is that I want to be able to chat with local models, remote models on my other machines, and cloud models (OpenAI API compatible). Anything that makes it easier to switch between models or query them simultaneously is important. Here's what I've learned so far: * Msty - my current favorite. Can do true simultan…

I've been building this: https://dinoki.ai/ Works fully local, privacy first, and it's a native app (Swift for macOS, WPF for Windows)

That's an interesting take on the topic! Bought it to support the development.
Post reply on HN