meetings VS embly

Compare meetings vs embly and see what are their differences.

meetings

WebAssembly meetings (VC or in-person), agendas, and notes (by WebAssembly)

embly

Attempt at building an opinionated webassembly runtime for web services (by embly)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
meetings embly
9 1
439 100
3.2% -
9.4 0.0
7 days ago about 3 years ago
HTML Rust
- -
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

meetings

Posts with mentions or reviews of meetings. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-01-26.

embly

Posts with mentions or reviews of embly. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-03-06.
  • Launch HN: Lunatic (YC W21) – An Erlang Inspired WebAssembly Platform
    5 projects | news.ycombinator.com | 6 Mar 2021
    Hey, I tried to build something like this too: https://github.com/embly/embly

    My takeaway after building that is that the build tooling is the major pain point. If you're trying to onboard someone onto this platform from their favorite language the hard part is getting from code to the .wasm file. wasm-bindgen (as an example) has put so much effort into build tooling, I wonder if that's a necessary path for success here.

    It's also great that WASI exists now, if I had to do embly again I'd just use wasi and then implement all of my "platform" features as filesystem features, not syscalls. If your API interface is the filesystem then you could provide interoperability between environments. Let's say you want to include a key-value store in the wasi runtime, you just make the keys files and the values file contents. Then you could so something like ship a FUSE filesystem to interact with the filesystem in the same way from a traditional VM or on a personal computer. I got really bogged down in custom syscalls and this path seems potentially more elegant.

    Have you also thought about live process migration? I got really excited about this from a technical standpoint. Since you completely control the runtime you could set up a clustered wasm solution that moves long running processes from VM to VM by sending their live memory state to another machine. Not sure if that's actually useful, but cool that it's not bogged down by the usual complexities of doing the same in a full OS environment.

    Anyway, so glad to see that someone is taking this idea on. Please make a cloud platform and let me pay for it. Also happy to chat more if any of this is useful, I've joined your discord as "max".

What are some alternatives?

When comparing meetings and embly you can also consider the following projects:

riscv-v-spec - Working draft of the proposed RISC-V V vector extension

interface-types

gc - Branch of the spec repo scoped to discussion of GC integration in WebAssembly

spec - WebAssembly specification, reference interpreter, and test suite.

chat - A telnet chat server

workers-rs - Write Cloudflare Workers in 100% Rust via WebAssembly

component-model - Repository for design and specification of the Component Model

diamond-types - The world's fastest CRDT. WIP.

dl_api - The easiest, simplest and safest way to load dynamic (shared object) libraries from Rust!

WasmCert-Isabelle - A mechanisation of Wasm in Isabelle.

grafbase - The future of APIs