Re:Introduction to WebAssembly Components
by chaz6 on Friday December 17, 2021 @09:48AM
(#29592861)
I think this could be a massive step forward for computing. Imagine if you will an add-on ecosystem for image editors like Krita or video editors like KdenLive. Add-ons could be distruted as a single package and can be run anywhere regardless of the system architecture or software plugin architecture, even within web applications. Write once, run anywhere.
[ Parent
| on HN ]
Re:Introduction to WebAssembly Components
by jcelerier on Friday December 17, 2021 @12:07PM
(#29594994)
i've been working on the "C++ API" side of this if you're interested :)
- https://github.com/celtera/avendish
- https://ossia.io/posts/reflection/
coupled with the definition of a common ABI, the holy grail of reusability may start to be closer
Isn't the memory barrier a huge penalty? (WASM can only access it's own memory, never the hosts.) I've been thinking about how WebAssembly could work server side to host websites, but every step seems to be copy bytes into or out of the VM.
Re:Introduction to WebAssembly Components
by PaulDavisThe1st on Friday December 17, 2021 @01:55PM
(#29596635)
> Write once, run anywhere
Where have I heard this before ....
Re:Introduction to WebAssembly Components
by ridruejo on Sunday December 19, 2021 @08:29AM
(#29613757)
That's exactly what is happening. It is just that this time it may actually work. For one thing, the industry as a whole (including Microsoft) is supportive of the standard and we have the benefit of 25+ years of hindsight
Re:Introduction to WebAssembly Components
by chaz6 on Saturday December 18, 2021 @01:35PM
(#29607128)
I did consider making a reference to Java but I decided against it as I thought it would be received in the spirit it was intended.
Re:Introduction to WebAssembly Components
by kingcharles on Friday December 17, 2021 @02:26PM
(#29597164)
1995 called; it wants its tag line back.