Interface-types Alternatives

interface-types reviews and mentions

• WebAssembly Playground
  9 projects | news.ycombinator.com | 4 Feb 2024

  Some things that might greatly increase wasm usage and overall tooling:

  1) Tools that run docker containers and serverless function services (like AWS lambda) to support providing a .wasm files instead

  2) Garbage collection in the runtime to make GC languages easier to port to wasm

  3) Dynamically typed languages (NodeJS, Python, Ruby) being able to compile to webassembly directly instead of porting the runtime to webassembly and then running the code through the runtime. This is a big ask though, basically needs to redesign the runtime completely

  4) wasm-DOM bindings will enable other languages to do HTML rendering which will require new web frameworks for every language that wants to take over the space from JS. This will lead to (even more) fragmentation of the web ecosystem

  5) A new wasm-first SDK (unrelated to the DOM) for building cross platform applications. I can see this taking off only if it is built-into the browsers and backed by some standards committee, so not very likely I think

  6) Something like the Interface Types proposal ( https://github.com/WebAssembly/interface-types/blob/main/pro... ) becomes a thing allowing wasm programs to be consisted of modules written in several different languages and being able to call said modules with low or 0 runtime performance hit (and of course, no compilation to multiple CPU archs). So much of programming ecosystems are locked to specific languages (like data science with python) when there is little technical reason for it be like that.

• Bring garbage collected programming languages efficiently to WebAssembly
  16 projects | news.ycombinator.com | 3 Nov 2023

  AFAIK GC is irrelevant for "direct DOM access", you would rather want to hop into the following rabbit hole:

  - reference types: https://github.com/WebAssembly/reference-types/blob/master/p...

  - interface types (inactive): https://github.com/WebAssembly/interface-types/blob/main/pro...

  - component model: https://github.com/WebAssembly/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 & Wasm (Safe and fast web development)
  1 project | /r/rust | 21 Sep 2022

  I'm not really optimistic that particular aspect will get much improvement. Many people expected interface types to come save the day, but after a looong stagnation that proposal has been archived (for now) in favour of component types, which has much less potential for performance gains.

• Plugins in Rust: Wrapping Up
  4 projects | /r/rust | 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 | /r/programming | 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 | news.ycombinator.com | 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: https://hacks.mozilla.org/2019/08/webassembly-interface-type...

  I don’t know if there’s a better intro article. I believe this is the current iteration of the proposal: https://github.com/WebAssembly/interface-types/blob/main/pro...

• Replace JS with Rust on front-end, possible? Advisable?
  7 projects | /r/rust | 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 | /r/programming | 15 Apr 2022

  I see no reason why not. See the interface types proposal for a proposed solution.

• Rust for UI development
  1 project | /r/rust | 27 Jan 2022
• Front-end Rust framework performance prognosis
  4 projects | /r/rust | 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 (https://github.com/WebAssembly/interface-types/blob/master/proposals/interface-types/Explainer.md) 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.

• A note from our sponsor - SaaSHub
  www.saashub.com | 23 Apr 2024

  SaaSHub helps you find the best software and product alternatives Learn more →