The Llama Ecosystem: Past, Present, and Future
1–10 of 40 posts
Re: The Llama Ecosystem: Past, Present, and Future
#2They didn't mention llama.cpp or show it in their picture, that's hopefully an oversight, it feels like a major slight. It's a (the?) major reason for llamas popularity.
I have mixed feelings, llama is great but it's perpetuated it's shitty license. They could have done so much more good if they'd used gpl style licensing, instead they basically subverted open source, using an objectively good model as leverage.
Re: The Llama Ecosystem: Past, Present, and Future
#3> There are now over 7,000 projects on GitHub built on or mentioning Llama. New tools, deployment libraries, methods for model evaluation, and even “tiny” versions of Llama are being developed to bring Llama to edge devices and mobile platforms.
Let’s say I want to find the latest or most recent projects on this, is it possible to find them on GitHub based on that criteria?
Re: The Llama Ecosystem: Past, Present, and Future
#4> There are now over 7,000 projects on GitHub built on or mentioning Llama. New tools, deployment libraries, methods for model evaluation, and even “tiny” versions of Llama are being developed to bring Llama to edge devices and mobile platforms. Let’s say I want to find the latest or most recent projects on this, is it possible to find them on GitHub based on that criteria?
Github has pretty varied filters, you can just search llama and sort by stars or recent activity etc. It doesn't look like it's possible to exclude python, but doing so might get you the "edge" ones. (Except they usually have python utilities for converting pytorch models)
Re: The Llama Ecosystem: Past, Present, and Future
#5> There are now over 7,000 projects on GitHub built on or mentioning Llama. New tools, deployment libraries, methods for model evaluation, and even “tiny” versions of Llama are being developed to bring Llama to edge devices and mobile platforms. Let’s say I want to find the latest or most recent projects on this, is it possible to find them on GitHub based on that criteria?
Github has pretty varied filters, you can just search llama and sort by stars or recent activity etc. It doesn't look like it's possible to exclude python, but doing so might get you the "edge" ones. (Except they usually have python utilities for converting pytorch models)
Oh? But you can’t sort by date or things like that?
Re: The Llama Ecosystem: Past, Present, and Future
#6Earlier quoted context omitted.
Github has pretty varied filters, you can just search llama and sort by stars or recent activity etc. It doesn't look like it's possible to exclude python, but doing so might get you the "edge" ones. (Except they usually have python utilities for converting pytorch models)
Oh? But you can’t sort by date or things like that?
See https://github.com/search/advanced there are various date options
Re: The Llama Ecosystem: Past, Present, and Future
#7They didn't mention llama.cpp or show it in their picture, that's hopefully an oversight, it feels like a major slight. It's a (the?) major reason for llamas popularity. I have mixed feelings, llama is great but it's perpetuated it's shitty license. They could have done so much more good if they'd used gpl style licensing, instead they basically subverted open source, using an objectively good model as leverage.
> It's a (the?) major reason for llamas popularity.
Absolutely not. There's a corner of the overall community that hovers it and overperceives it as everyone else only uses it too.
Its great if you have an Apple ARM machine and want to see an M2 Pro do 10 tokens/sec (and what could make an Apple ARM have 30 minute battery life).
I also doubt it's a slight, the only callouts are large commercial collaborations, ex. nVidia, AMD, Google are representative of each of the 3 groups we could assign it
Re: The Llama Ecosystem: Past, Present, and Future
#8People on HN like to complain about the license all the time like a crusade but I’m personally very thankful for their work and the community that is building off of it. I recently setup Ollama + codellama + continue dev and it’s game changer. Practically have been a drop in github copilot replacement but local.
Re: The Llama Ecosystem: Past, Present, and Future
#9People on HN like to complain about the license all the time like a crusade but I’m personally very thankful for their work and the community that is building off of it. I recently setup Ollama + codellama + continue dev and it’s game changer. Practically have been a drop in github copilot replacement but local.
Yeah the community is great.
It’d just be better if it was around RWKV or something that doesn’t prevent you from improving any models outside of the llama ecosystem.
It’s a great embrace, extend, extinguish play by meta.
Re: The Llama Ecosystem: Past, Present, and Future
#10They didn't mention llama.cpp or show it in their picture, that's hopefully an oversight, it feels like a major slight. It's a (the?) major reason for llamas popularity. I have mixed feelings, llama is great but it's perpetuated it's shitty license. They could have done so much more good if they'd used gpl style licensing, instead they basically subverted open source, using an objectively good model as leverage.
> It's a (the?) major reason for llamas popularity. Absolutely not. There's a corner of the overall community that hovers it and overperceives it as everyone else only uses it too. Its great if you have an Apple ARM machine and want to see an M2 Pro do 10 tokens/sec (and what could make an Apple ARM have 30 minute battery life). I also doubt it's a slight, the only callouts are large commercial collaborations, ex. nV…
I'd be curious if you have any hard data about use. Mine is anecdotal too, but I see that llama.cpp is the very close second highest starred repo with llama on the name, after meta llama. Additionally, all the HF models seem to have ggml / gguf quantized versions . I'm not aware of a competing format for quantized models. There are also python bindings which are used in a lot of projects. What is a competing framework, other than pytorch, that's getting more use? Or is it all just pytorch (and some hf wrappers) and the rest is a rounding error?