By WebAssembly

Interface-types Alternatives

Similar projects and alternatives to interface-types

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

interface-types reviews and mentions

Posts with mentions or reviews of interface-types. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-07-27.
  • Plugins in Rust: Wrapping Up
    4 projects | | 27 Jul 2022
    Really good questions. Unfortunately, most of the issues I found back then were fundamental ones. I've seen that Wasm has deprecated "Interface Types" and is now working on the "Component Model". But even then, as far as I understand that would only avoid the serialization and deserialization steps, and you would still need to copy complex types. It will be more performant, but I don't think it would be enough for Tremor either.
  • When moving from JS to WASM is not worth it - Zaplib post mortem
    3 projects | | 30 Apr 2022
    wasm doesn't know anything about the outside world on purpose. This allows it to be used in other domains. For direct access to the DOM et al, interface types are being developed. It's a non-trivial problem to interoperate with a dynamically typed GC'd language from any statically typed no-GC language that can compile to wasm.
  • WebAssembly 2.0 Working Draft
    21 projects | | 19 Apr 2022
    The whole list of proposals and where they're at is here:

    You can see that "interface types" is at "Phase 1 - Feature Proposal (CG)", so still early days.

    And there's a link to the proposal here, for people like me who don't know about it:

    21 projects | | 19 Apr 2022
    You may want to look into WASM interface types, which is defining what amounts to am IDL for WASM and different languages have common calling conventions:

    I don’t know if there’s a better intro article. I believe this is the current iteration of the proposal:

  • Replace JS with Rust on front-end, possible? Advisable?
    7 projects | | 17 Apr 2022
    Yes, and if I'm not mistaken, this is the RFC
  • Google Chrome emergency update fixes zero-day used in attacks
    4 projects | | 15 Apr 2022
    I see no reason why not. See the interface types proposal for a proposed solution.
  • Front-end Rust framework performance prognosis
    4 projects | | 15 Jan 2022
    Wanted to get thoughts from the Rust experts on this - the author of the Yew framework seems to think that Web Assembly Interface Types ( will allow Yew to eventually become faster than Vue, React, Angular, etc. Is there general consensus on this in the Rust community? The prospect of mixing Rust (for the performance critical pieces) with TS on the front end doesn't seem super appealing to me.
  • VSCode terminal from DOM to >canvas<
    3 projects | | 25 Dec 2021
    I can't help but feel like this is the worst. Every time we step away from HTML & the DOM & into a further farther reach of abstraction, into something custom crafted & artisinal, we lose our valuable common heritage. We flea from common understandability & recurse into something ever more unique & virtual.

    In the process- as is the case with Google Docs[1]- we lose things like the ability for web extensions to work, if this is a web hosted vscode instance (vscode server, openvscode, code-server, others). Running a debugger against this part of vscode- web or native- now yields only garbage junk information.

    Right now this is just the terminal. I think- "it could be worse". But it chills me deeply that the terminal is now no longer real information. It's now just a happenstance jumble of pixels, powered by only it's own inner logic & a unique maze of libraries. Big tech keeps optimizing and optimizing, & the motive we keep being sold- this is for your good, this helps you- is one I frankly have a very hard time negotiating with myself. De-webbifying the web, de-commonizing the common platform- as Facebook has done by virtualizing the DOM- feels like this ever-running big-bang from a truthful original universe into a sparse, cold, expanding universe where each little fragment defines itself, where the common hypertext medium no longer means anything.

    I keep waiting for some moments of contraction, some coming back together, for things to make more sense again, to recontract into something more solid. React's first WebComponents PR[2] is a notable re-contracting, re-platforming- a powerful act I frankly didn't expect, so rare as to feel practically unprecedented.

    I realize much of this flexibility, the demonstrated versatility of the web & usage of the various pieces of it represents much of it's strength. The platform being a low-level platform where higher level platforms can be created is amazing; the Extensible Web Manifesto[3] speaks to that emergence of newer higher levels systems. And right now we're in early days, just starting a precambrian explosion of higher level web, as technology like WebAssembly only just begins to become real- still so early, still way pre-pre- Interface Types[4]/Host Bindings, only just the crudest emulation beginning in via projects like Rust's wasm-bindgen / web-sys. I am happy we are still exploding. We have so much more to exlpore. But gee I also question so much when big enterprises turn hypertext into pixels. To move compute into webassembly is a bold leap but the hypertext can survive, the DOM is still truth. It's so uncertain to me, feels like so much might be lost when giants like Microsoft or Google yank out the HTML & replace it with pixels, pushed into our faces. It feels like betrayal, like sabotage, like we're giving up truth.


    [2] (16 days, 0 comments)



  • How is Redox OS (and similar projects) planning to deal with the lack of dynamic linking support?
    5 projects | | 10 Nov 2021
  • Masked input control for Blazor?
    4 projects | | 12 Sep 2021
    The tracking issues there gets updated when it changes phases and each proposal has it's own repo for discussion or how it works overall. For interface types it's this repo
  • A note from our sponsor - SonarQube | 7 Dec 2022
    Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free. Learn more →


Basic interface-types repo stats
7 months ago
Static code analysis for 29 languages.
Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free.