There’s a GitHub link which is open from last year, about the missing license in ollama. They have not bothered to reply, which goes to show how much they care. Also it’s a YC company, I see more and more morally bankrupt companies making the cut recently, why is that?
Readit Newsam17an commented on Ollama and gguf github.com/ollama/ollama/... · Posted by u/indigodaddy
am17an commented on How attention sinks keep language models stable hanlab.mit.edu/blog/strea... · Posted by u/pr337h4m
This is nice and useful because the new GPT-OSS model uses this technique. Kudos to the original authors!
Ollama is great but I feel like Georgi Gerganov deserves way more credit for llama.cpp.
He (almost) single-handedly brought LLMs to the masses.
With the latest news of some AI engineers' compensation reaching up to a billion dollars, feels a bit unfair that Georgi is not getting a much larger slice of the pie.
Seriously, people astroturfing this thread by saying ollama has a new engine. It literally is the same engine that llama.cpp uses and georgi and slaren maintain! VC funding will make people so dishonest and just plain grifters
totally respect your choice, and it's a great project too. Of course as a maintainer of Ollama, my preference is to win you over with Ollama. If it doesn't meet your needs, it's okay. We are more energized than ever to keep improving Ollama. Hopefully one day we will win you back.
Ollama does not use llama.cpp anymore; we do still keep it and occasionally update it to remain compatible for older models for when we used it. The team is great, we just have features we want to build, and want to implement the models directly in Ollama. (We do use GGML and ask partners to help it. This is a project that also powers llama.cpp and is maintained by that same team)
I’ve never seen a PR on ggml from Ollama folks though. Could you mention one contribution you did?
"You're just prompting it wrong. Did you:
1. set up your dozens of /\.?claude.*\.(json|md)/i dotfiles? 2. give insanely detailed prompts that took longer to write than the code itself? 3. Turn on auto-accept so that you can only review code in one giant chunk in diff, therefore disallowing you to halt any bad design/errors during the first shot?"
> ...easy to hit the 5 hour window limit in just 2 hours
I've had this experience. Sucks especially when you're working in a monorepo because you have client/server that both need to stay in context.
Asymptotically, prompting is a programming language.
am17an commented on “Good first issues” are usually not good first issues am17an.bearblog.dev/why-g... · Posted by u/am17an
> I just wish more projects took the time to making this page more useful. When you create a "good first issue", think of it as paying it forward. You enter a contract with a fragile newbie; be precise, helpful and unassuming.
I love this. It’s no surprise that OSS projects need the occasional backlog grooming.
> But I've found this page to be downright helpful in most cases.
Perhaps you meant to say “UNhelpful”?
> Perhaps you meant to say “UNhelpful”?
Yes, thanks for pointing it out!
am17an commented on Generative AI. "Slop Generators, are unsuitable for use [ ]" asahilinux.org/docs/proje... · Posted by u/aleksjess
In the future there will be safe havens where LLM generated code has not been merged. It will marketed as “hand-crafted” by Romanian programmers or something like that, akin to Swiss watches. It will be extremely high quality, but too expensive to mass produce.
am17an commented on “I noticed a clear violation of our contributing guidelines” github.com/antiwork/flexi... · Posted by u/slacktivism123
There's going to a wrapper around github PRs to summarize these issues, the mess they created in the first place. BTW this is the same guy which has famously stopped hiring engineers