4 ms·
If you want a plugin-in system, maybe don't pick a language with static linking, and an half-backed plugin implementation in first place. WebAssembly outside o
by pjmlp 2y ago
If you want a plugin-in system, maybe don't pick a language with static linking, and an half-backed plugin implementation in first place.
WebAssembly outside of the browser is a solution looking for a problem that has been sorted out multiple times since the idea of bytecode based execution exist, 1958 to be more precise.
Even on the browser its use, besides bringing back the old plugins is debatable, using GPU compute is much better for number crunching, with much better tooling.
- coder543 2y agoYes… I’m aware of the history. I’m also aware that WASM solves problems that those previous ones didn’t. Otherwise you would have provided an option that actually met the requirements, if there are so many to choose from. > If you want a plugin-in system, maybe don't pick a language with static linking Or… a plugin system could “just work”, without placing unnecessary restrictions on what I do.
- pjmlp 2y agoIt starts by choosing the right language for the job.
- apitman 2y agoThe right language for a plugin system is the one that attracts the most plugin writers. Supporting many languages is a huge boon for wasm in this department. It's one of the things that makes the JVM and .NET so appealing in the first place, but WASM is better than both combined when it comes to language selection.
- pjmlp 2y agoThat surely isn't any WebAssembly then, if we are counting adoption growth throughout computing history.
- deleted 2y ago[deleted]
- orf 2y agoHow do I prevent my statically linked plugins from having any filesystem access, or a bug messing with memory it doesn’t control once it’s loaded?