awesome-wasm-runtimes VS AnswerOverflow

Firecracker is a fine technology, but serverless companies have started taking advantage Wasm's faster start-up times for use cases of running Wasm on the server (https://www.youtube.com/watch?v=yqgCxhPAao0). The deny by default security policy makes Wasm a great choice to run your code in isolation, particularly for maximizing hardware resources in the multi-tenant environments these serverless companies operate.

In the past few years, we have seen more use cases of Wasm emerge outside of the browser. JavaScript engines are now just a fraction of the total number of runtimes available. Wasmtime, Wasmer, WasmEdge, wazero are popular ones for non-browser use cases like blockchain, serverless, and edge computing (although Cloudflare uses V8's Wasm engine). WAMR is a popular one for cyber physical/IoT devices. There's a nice list here: https://github.com/appcypher/awesome-wasm-runtimes

There's plenty of other ways to interact with Wasm, most of which are secure. (Wasmtime is the one I'm most familiar with, which is why I linked to it.)

Yeah, this is one of many non-browser runtimes, e.g. see https://github.com/appcypher/awesome-wasm-runtimes

Lunatic is more opinionated than most of these or node, though, in that it's trying to emulate a particular concurrent system design pattern borrowed from Erlang/BEAM.

There's an overview of different WASM runtimes with features: https://github.com/appcypher/awesome-wasm-runtimes

Now, the creation Bytecode Alliance, the development of multiple WebAssembly runtimes and the work of the W3C WebAssembly Community Group is why I belive it will get popular, but the capability-based security model is why I want it to get popular.

⚖ I think it's really cool that a plugin author could compile their C++ to .wasm such that a single plugin binary can run on either Linux or Windows (don't need an x86 .dll, x64 .dll, x86 .so, x64 .so...) and in a sandbox (no arbitrary syscalls or Win32 calls, just the interfaces given to it), while still getting near native AOT speed. Though, it's hard to judge which one to choose from now with all the wasm engines that are available (https://github.com/appcypher/awesome-wasm-runtimes), with wasmtime or inNative being two others I've considered for my project. I'll definitely look into this one though, given it supports many of the newer proposals.

Numerous native runtimes for webassembly already exist[0], with the current popular choices apparently being Wasmer[1] and Wasmtime[2].

All one would need to do (AFAIK) is ship a client for all major platforms, as is done with Electron (and web browsers themselves, and everything else.)

[0]https://github.com/appcypher/awesome-wasm-runtimes

> TOO many bots log entire channels out to public html sites. This is prevalent in everything like discord etc but the degree to it in IRC is just ridiculous god knows what any of those 1500 bots in a channel are doing.

These sorts of bots are quite rare on Discord, you usually have to make an account to be able to see anything. There have been attempts at standardizing this (like https://www.answeroverflow.com/) but they haven't taken off. Public logs are much more common on IRC than on Discord.

Related: AnswerOverflow makes Discord messages searchable on Google/ other search engines. It’s open source.

https://www.answeroverflow.com/

I agree that the discord centralization for Q&A is becoming problematic, it makes it less discoverable and searchable (Had this problem a lot with Svelte).

That said, I have had success so far using https://www.answeroverflow.com/ to search discord for questions. It sucks we have to use such tools, but given the current situation, it's also better to adapt.

We've started mirroring our Discord to the web using https://www.answeroverflow.com/

You could roll your own equivalent but AnswerFlow has some nice features and handles issues around consent nicely.

If you're starting a Discord then I'd strongly recommend stating upfront that you might mirror content to another location even if you're not doing it now - it makes it a lot easier than doing so further down the line.

A better solution would be to not use Discord but friction, push-back from my colleagues on alternatives and a fear of fragmenting the community made this the best option for us.