291–299 of 299 posts
Earlier quoted context omitted.
I think having a bash script as the linux installation is more of a stop-gap measure than truly supporting Linux. And ollama is FOSS compared to LM Studio and Msty (as someone who switched from ollama to LM Studio; I'm very happy to see the frontend development of ollama and an easier method of increasing the context length of a model).
lol the Ollama app is closed source
Earlier quoted context omitted.
Yes I do that too. The important bit is the model. Rest is almost trivial. I had posted a Show HN here about the script I've been using which is open source now ( https://github.com/n-k/tinycoder ) ( https://news.ycombinator.com/item?id=44674856 ). With a bit of help from ChatGPT etc., it was trivial to make, and I use it everyday now. I may add DDG and github search to it soon too.
this is not coder this help typing instructions. Coding is different. For example look at my repository and tell me how refactorizing it, write a new function etc. In my opinion You must change name.
> this is not coder this help typing instructions.
'Coding' technically is just that. If you mean engineering, yes sure, I agree. Nothing right now automates engineering. Maybe some day.
I tried Ollama once but immediately removed it, when I couldn't easily install models that are outside of the models they "support". LM Studio is by far the best tool out there in my humble opinion.
OLLAMA is a great app, and so is Lmstudio, but HugstonOne offers better experience.
I couldn't find the source for the new app, is it open source like the cli or is it rather closed?
Looks like a big pivot on target audience from developers to regular users, at least on the homepage https://ollama.com/ as a product. Before, it was all about the CLI versions of Ollama for devs, now it's not even mentioned. At the bottom of the blog post it says: > For pure CLI versions of Ollama, standalone downloads are available on Ollama’s GitHub releases page. Nothing against that, just an observation. Previou…
one of the maintainers for Ollama. I don't see it as a pivot. We are all developers ourselves, and we use it. In fact, there are many self-made prototypes before this from different individuals. We were hooked, so we built it for ourselves. Ollama is made for developers, and our focus in continually improving Ollama's capabilities.
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…
- I still appreciate the simplicity to the point where I use it more the Open WebUI - no logins, no settings, just chat
- I wish the model select in the chat box was either moved or was more subtle, currently it visually draws interest to something that doesn't change much
- Chat summaries sometimes overflow in the chat history area
- Small nit but the window uses the default app icon on Windows rather than the Ollama icon
In addition to what others have said, I've had great experiences with LobeChat: https://github.com/lobehub/lobe-chat
> b. a commercial license must be obtained from the producer if you want to develop and distribute a derivative work based on LobeChat.
Earlier quoted context omitted.
Choice is good but here is why prefer Ollama over others (I'm biased because I work on Ollama). Supporting multiple backends is HARD. Originally, we thought we'd just add multiple backends to Ollama - MLX, ROCm, TRT-LLM, etc. It sounds really good on paper. In practice, you get into the lowest common denominator effect. What happens when you want to release Model A together with the model creator, and backend B doesn…
Sure, those are all difficult problems. Problems that single devs are dealing with every day and figuring out. Why is it so hard for Ollama? What seems to be true is that Ollama wants to be a solution that drives the narrative and wants to choose for its users rather than with them. It uses a proprietary model library, it built itself on llama.cpp and didn't upstream its changes, it converted the standard gguf model…