Repository for design and specification of the Component Model (by WebAssembly)

Component-model Alternatives

Similar projects and alternatives to component-model

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better component-model alternative or higher similarity.

component-model reviews and mentions

Posts with mentions or reviews of component-model. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-04-13.
  • Tree-shaking, the horticulturally misguided algorithm
    6 projects | | 13 Apr 2024
    I don't think that's a very good goal. Jettisoning the DOM means jettisoning accessibility and being able to leverage everything that the browser gives you out-of-the-box. You have to render to a canvas and build everything from scratch. I think Wasm is great for supplementing a JS app, not replacing it (e.g. using a Wasm module to do some calculations in a Worker). I like to use the right tool for the job, and trying to use something other than JS to build a web app just seems a little janky to me.

    At one point, there was a Host Bindings proposal that would enable you to do DOM manipulation (it looks like it was archived and moved to the Component Model spec [1]). That would probably be the ideal way to avoid as much JS as possible. However, browser vendors have been heavily optimizing their JS runtimes, and in some cases, Wasm may actually be slower than JS.

    I've been following Wasm's progress for several years, which has been slow, but steady. Ironically, I think the web is actually the worst place to use it. There's so much cool non-web stuff being done with it and I'm more interested to see where that goes.


  • 3D and 2D: Testing out my cross-platform graphics engine
    17 projects | | 2 Apr 2024
    Well the great thing about WebAssembly is that you can port QT or anything else to be at a layer below -- thanks to WebAssembly Interface Types[0] and the Component Model specification that works underneath that.

    To over-simplify, the Component Model manages language interop, and WIT constrains the boundaries with interfaces.

    IMO the problem here is defining a 90% solution for most window, tab, button, etc management, then building embeddings in QT, Flutter/Skia, and other lower level engines. Getting a good cross-platform way of doing data passing, triggering re-renders, serializing window state is probably the meat of the interesting work.

    On top of that, you really need great UX. This is normally where projects fall short -- why should I use this solution instead of something like Tauri[2] which is excellent or Electron?




  • Missing the Point of WebAssembly
    2 projects | | 9 Jan 2024
    While I don't necessarily agree with the unnecessary, unsupported casual, & cheap contempt culture here ("unshackle the web from the mess that is JavaScript", "places that don't really need these problems to be solved")...

    WebAssembly component-model is being developed to allow referring to and passing complex objects between different modules and the outside world, by establishing WebAssembly Interface Types (WIT). It's basically a ABI layer for wasm. This is a pre-requisite for host-object bridging, bringing in things like DOM elements.

    Long running effort, but it's hard work and there's just not that many hands available for this deep work. Some assorted links with more:

    It's just hard work, it's happening. And I think the advantages Andy talks to here illuminate very real reasons why this tech can be useful broadly. The ability to have plugins to a system that can be safely sandboxed is a huge win. That it's in any language allows much wider ecosystem of interests to participate, versus everyone interested in extending your work also having to be a java or c++ or rust developer.

  • Steel – An embedded scheme interpreter in Rust
    13 projects | | 3 Dec 2023
    A. Sure, but it isn't sufficiently beneficial for the cost.

    B. WebAssembly is immature for developing a plugin system because of the lack of a sufficient ABI:

    C. There aren't any other languages that meet the criteria. Lua was a no-go from the start. The maintainers did not like the language, and it necessitated adding more C code to Helix which could complicate building even further.

  • Bring garbage collected programming languages efficiently to WebAssembly
    16 projects | | 3 Nov 2023
    AFAIK GC is irrelevant for "direct DOM access", you would rather want to hop into the following rabbit hole:

    - reference types:

    - interface types (inactive):

    - component model:

    If this looks like a mess, that's because it is. Compared to that, the current solution to go through a Javascript shim doesn't look too bad IMHO.

  • Rust Is Surging Ahead in WebAssembly (For Now)
    2 projects | | 19 Oct 2023
    The wasm idl (called WIT) is actively being worked on here:

    Being able to access DOM is definitely an objective. It's just taking a lot longer than folks guessed to build a modular wasm ABI.

  • Reaching the Unix Philosophy's Logical Extreme with WebAssembly
    6 projects | | 28 Aug 2023
    The WASM Component Model

  • WASI: WebAssembly System Interface
    6 projects | | 5 Aug 2023
  • Introducing - Wasmer Runtime 4.0
    3 projects | /r/rust | 22 Jun 2023
    Take a look at the python abi to see what the structure looks like for calling into components
  • How WebAssembly Is Eating the Database
    1 project | | 23 May 2023
  • A note from our sponsor - SaaSHub | 24 May 2024
    SaaSHub helps you find the best software and product alternatives Learn more →


Basic component-model repo stats
7 days ago

SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives