Hacker News new | ask | show | jobs
by superkuh 926 days ago
It only takes away choice if you use the demo files with the models baked in. There are versions of this under the Releases->Assets that are only the actual llama.cpp OS portable binaries that you pass the model file path to as normal.

Compiling llama.cpp is relatively easy. Compiling llama.cpp for GPU support is a bit harder. I think it's nice this OS portable binaries of llama.cpp applications like main, server, and llava exist. Too bad there's no opencl ones. The only problem was baking in the models. Downloading applications off the internet is not that weird. After all, it's the recommended way to install Rust, etc.
1 comments
wokwokwok 926 days ago
> Compiling llama.cpp is relatively easy. Compiling llama.cpp for GPU support is a bit harder.

It is not.

For Mac using M1 as per this specific post, you run “make”.

If you have an older Intel Mac and have to run using cpu, you run “make”.

> Downloading applications off the internet is not that weird. After all, it's the recommended way to install Rust, etc.

Downloading applications from trusted sources is not that weird.

Eg. Rust, from the rust organisation.

Downloading and running user uploaded binaries is a security nightmare.

link
paolop 926 days ago
While in general I agree with your security concerns, here the links are from very trusted sources (Mozilla Internet Ecosystem and Mozilla's innovation group) and the user is well known (present on X too with a large following).

Re: "simplicity", sure for you and I it's simple to compile llama.cpp, but it's like asking a regular user to compile their applications themselves. It's not that simple for them, and should not be required if we want to make AI and OSS AI in particular more mainstream.

link
wokwokwok 926 days ago
The command to run is:

Open terminal

curl -LO https://huggingface.co/jartine/llava-v1.5-7B-GGUF/resolve/ma...

chmod 755 …

./…

Open localhost:8080 in browser

To make this accessible to a broader cohort you would package it into an app and put it somewhere with provenance, eg. A well known GitHub account or App Store.

The solution, as shown, doesn’t solve either of the problems you’ve said are problems it attempts to solve.

It is a bad solution.

link
paolop 926 days ago
Totally agreed it's not yet ideal - absolutely. But I feel we are expanding the pie of users with this step, which is just an intermediate step. Do you want to work on that packaging ;-)?
link