Closed Kroeg93 closed 2 years ago
Hi, we are focusing all our efforts on Wasmtime these days, and don't suggest using Lucet for new projects. For the last year or so Lucet is only getting minor updates to its dependencies (we track updates to cranelift) and some improvements required for Wasmtime feature parity. We suggest all users switch to Wasmtime as soon as they can - it now has all of the features that previously only Lucet had, like AOT compilation and userfaultfd-based memory pooling.
Allright, thanks!
@pchickey Thanks for the update!
Maybe add a short note in the readme about this? Just one line or two. Took me a while to figure out that it's all happening in wasmtime now.
Thanks for the suggestion, I meant to put such a notice up a long time ago. Sorry this information was hard to find.
@pchickey Thanks!
Hey all,
I dont know whether this is the right place for this but i try to get my head around the lucet project for quite a while know because i want to create a small rust faas-application which embeds the lucet toolchain. You all do a great job! :-)
But something that makes me a little bit confused is the documentation about this project because some parts of it seem to be very outdated. For example within lucetc there are many different options like witx_specs, wiggle_bindings or veriwasm (there are other, too) which are not documentated (But which are very important).
In a very rapidly changing ecosystem like wasm this makes it sometimes really hard to stay on track with that project. Maybe there are other people thinking the same? Is there any documentation i maybe not found? Currently the repo is my first source of documentation about lucetc/lucet-wasi/etc. but there are some parts which are hard to understand.