The APE shell script needs to run /bin/mkdir in order to map the embedded ELF executable in memory. It should be possible for you to work around this on Linux by installing our binfmt_misc interpreter:
sudo wget -O /usr/bin/ape https://cosmo.zip/pub/cosmos/bin/ape-$(uname -m).elf
sudo sh -c "echo ':APE:M::MZqFpD::/usr/bin/ape:' >/proc/sys/fs/binfmt_misc/register"
sudo sh -c "echo ':APE-jart:M::jartsr::/usr/bin/ape:' >/proc/sys/fs/binfmt_misc/register"
That way the only file you'll need to whitelist with Nix is /usr/bin/ape. You could also try just vendoring the 8kb ape executable in your Nix project, and simply executing `./ape ./llamafile`.
It's especially disappointing to see Deno doing this, because in the past they've used endearing art made by an artist, hashrock, which I liked very much.
Relevant but not mentioned: syrusakbary is the CEO of Wasmer, the company behind WASIX. I'm personally excited by WASIX (WASI has stagnated too long), but if you recommend something you have a part in, I think you should mention it.
The guy that tried to trademark the Webassembly name btw and it's constantly trying to hijack the community with halfbaked solutions instead of pushing forward the standard, cause Wasmer had beef in the past with bytecode alliance peeps.
WASI and WASM move slow for a good reason, This is how proper science and engineering works. The "go fast and break things" mentality of silicon valley startups has mainly filled the industry with low quality software.
I imagine Wasmer must be in a bit of a difficult place right now. My understanding is that they are VC-backed (YC?), which means they're essentially trying to figure out how to make a huge amount of money off an open standard or something adjacent to it. But then, they would have known this from the very start, so I'm not sure what they expected, or why a VC firm would even look at them as a promising prospect.
Maybe they hoped to be like Docker, where the value-add was cohesive higher-level tooling on top of all the lower-level bits. If that's the case, then WASI would be an existential threat in that it (and the tooling people are building around it) commoditizes what would otherwise be Wasmer's special sauce. I'm speculating wildly, of course, but it would at least be consistent with Wasmer's/Sirius's apparent vendetta against WASI and the people working on it.
I hope Wasmer eventually finds a way to add value that doesn't rely on constant gaslighting and white-anting the standards process.
My response is focused here to be as productive as possible, and intentionally doesn't enter your other comments about Wasmer or my persona as, while incredibly accurate, I want to make sure we keep conversation properly railed.
We recently presented Wasmer Edge [1], for which developers, enterprises and VC firms are incredibly excited for it as it brings a more scalable approach for both Cloud and Edge computing. Please give it a try and let us know if you have any questions!
I wonder why the need to post hateful/flamewar comments in all the Hacker News posts where Wasmer is mentioned [1] [2] [3].
In my last comment on a previous thread [1], I asked a direct question to see if you are related at all to the BA, without success. I'd love if you can bring some light on this, and I'd appreciate if you can do so without trying to start a flamewar.
hey, I am not affiliated with BA at all. I just don't like you and what you represent. The filth of silicon valley startups that try to make money off of the hard work and love some people put on their projects. Open source peeps do not need your pathetic public apologies which is obvious just another marketing strategy since you relized you f'ed up.
Runtimes didn't wait for WASIX to start adding missing system calls to WASI.
But WASIX brings a central place to document all this.
And I don't think WASIX is fundamentally incompatible with the future WASI. The different ABIs doesn't make this straightforward, but WASIX could be available as WASI extension like others.
[1] https://observablehq.com/documentation/cells/javascript#nami...
[2] https://observablehq.com/documentation/cells/javascript#expr...