rutie VS wasmer

For example, they list PyO3 for Python (see also maturin for packaging), NAPI-RS for Node.js, and Rutie for Ruby.

If this sounds useful you should also take a look at rutie, another library that does the same thing and has been around longer.

I'm not the first person to have this idea, there's also the great rutie. I make no claims that Magnus is any better, it's just my attempt at it.

I did some tinkering before with excelent rutie gem, which enables writing ruby libraries with rust as native extension, so was wondering if I could use that one + ripgrep for faster searches.

hlua or rlua are what you want for Lua, rust-cpython or PyO3 for Python, rutie for Ruby, and possibly deno_core for JavaScript.

I was at first using mrusty, then I switched to rutie, because I thought mrusty didn't support blocks (it does, it's just he documentation for it is easily missed, it's in the docs for the for the mrfn! macro, right near the bottom of the page), so I'm switching back (haven't yet started on this redo) because it has what I want & it's easier to use.

If writing the whole API in Rust is too big of a sell for your employer, I highly recommend checking out rutie or helix (running native rust modules from ruby).

Helix (https://github.com/tildeio/helix) is deprecated though. The only candidate alive enough seems to be Rutie (https://github.com/danielpclark/rutie). At least you don't risk putting people in the wrong direction! I think I will buy the book, from skimming it seems cool!

This is awesome. I'd love to have upstream support in Wasmer ( https://wasmer.io )

WebAssembly is extremely portable. WebAssembly runs on: all major web browsers, V8 runtimes like Node.js, and independent Wasm runtimes like Wasmtime, Lucet, and Wasmer.

Unfortunately cosmopolitan wouldn't work for dockerc. Cosmopolitan works as long as you only use it but container runtimes require additional features. Also containers contain arbitrary executables so not sure how that would work either...

As for WASM, this is already possible using container2wasm[0] and wasmer[1]'s ability to generate static binaries.

[0]: https://github.com/ktock/container2wasm

[1]: https://wasmer.io/

I could not find any guide how to add WASM container capability to Docker running on Colima. This guide provides a few Colima templates for exactly this, which adds WasmEdge, Wasmtime and Wasmer runtime types.

Just suggested as well Wasmer on Twitter! https://github.com/wasmerio/wasmer

Looking forward to seeing the results :)

The Biome team has been incredibly fast on solving the challenge and achieving 95% compatibility with Prettier [1]

Just as a note, as it was not mentioned in the article, Wasmer [2] also participated with a $2,500 bounty to compile Biome to WASIX [3], and it has been awesome to see how their team has been working to achieve this as well... hopefully we'll get Biome running in Wasmer soon!

Keep up the great work!!

[1] https://github.com/biomejs/biome/issues/720

[2] https://wasmer.io/

[3] https://wasix.org/

It's funny how WebAssembly can help overcome most of the issues mentioned on the blogpost (packaging, configuration, portability) if addressed properly.

That's the main reason Wasmer [1] was created :)

[1] https://wasmer.io

Thanks for the mention to Wasmer.

I'll put here a link in case is useful for future readers: https://wasmer.io/