threads
webcontainer-core
Our great sponsors
threads | webcontainer-core | |
---|---|---|
16 | 20 | |
668 | 3,622 | |
2.7% | 1.9% | |
2.0 | 2.0 | |
4 months ago | about 1 year ago | |
WebAssembly | ||
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
threads
-
No installation required: how WebAssembly is changing scientific computing
Similarly for threads: https://github.com/webassembly/threads
-
WebAssembly: Adding atomics waits to the main thread is the right thing to do
Specifically I submitted this to draw attention to the latest comment in the thread: https://github.com/WebAssembly/threads/issues/177
It's a good deep dive into how a small, but well-intentioned, browser choice nearly a decade ago led to poor outcomes for the WebAssembly ecosystem.
-
WASI Support in Go
The answer is: it's complicated. Which is most of the time the answer in the WASI world.
For this case it's complicated because some runtime supports https://github.com/WebAssembly/threads which mostly contains things like the spec for atomic but not the actual "threads" specs and then some runtimes (i.e wasmtime) also supports https://github.com/WebAssembly/wasi-threads which is one version of the threads. But a new proposal came into play https://github.com/abrown/thread-spawn so ... it's complicated.
-
WASM is the future?
There’s a proposal for threads
- Bringing Git in the browser via Go and WebAssembly. Upload, create files, folders, branches, commits etc... On the fly in the browser
-
LibreOffice running natively in a browser via WebAssembly
WebAssembly is having/going to have threads
https://github.com/WebAssembly/threads
-
The State of WebAssembly â 2021 and 2022
It's disappointing to see the WebAssembly/threads proposal is still only in proposal state, despite existing since 2018. It being just a proposal stops languages like golang from actually implementing support for it, despite Chrome supporting it since v70.
-
Using WebAssembly threads from C, C++ and Rust
Ah, I should have clarified that I mean the assembly instructions for atomics, rather than the JavaScript API. I.e. the opcodes listed here: https://github.com/WebAssembly/threads/blob/master/proposals...
-
AMA: We are Akhi, Alexandra, Islam, and Dimitris from the DFINITY Execution team. Ask us anything about building the execution layer.
Another point to add here is that the current wasm specification does not support threads although there is a proposal to add one. So I imagine that till the wasm specification includes it, we will continue to have only single threaded canisters.
webcontainer-core
-
API Security Academy dedicated to GraphQL security
How does it work? There is no backend whatsoever. The API Security Academy leverages WebContainers, a new technology that allows running full-blown node instances directly in the browser. Each WebContainer contains a live GraphQL application, so you'll not only understand why a vulnerability is risky, but also how to exploit it and, most importantly, how to fix it.
-
Node on Web. Use Nodejs freely in your browser with Linux infrastructure.
StackBlitz made the claim "... run Node.js, entirely inside your browser" #658, then had to revise it's claim to "We currently do not expose a way to use WebContainer outside of StackBlitz.com,".
-
Lua: The Little Language That Could
> Wasm though seems like the likely general heir, and will have many different offerings for how to do that (Deno being one!).
I was recently blown away by some ideas that StackBlitz [0] apply based on WebContainers. The idea of a "server in the browser", they allow you to run Node-based environment like that via Wasm.
[0] https://stackblitz.com/
[1] https://webcontainers.io/
-
How repl.it and online code editors are built?
See https://webcontainers.io.
-
Blog Post: Reasonable Bootstrap
This very simple fact is well known flaw, which was already often criticized and asked for solutions by users. It doesn't only affect this kind of very exotic bootstrap applications but also significantly limits rusts usefulness in many other areas. Pure browser based scientific code documentation and example notebooks (e.g. jupyterLite) and sandboxed CI and IDE solutions (e.g. web containers) as available for many other languages are simply not available for rust because of this very fundamental issue.
-
WebContainer API
Looks like they plan to open it. From the FAQ section of README (https://github.com/stackblitz/webcontainer-core#faqs):
> Is there a developer API?
-
[AskJS] Is there an JavaScript engine agnostic server module that can be imported into Bun, QuickJS, Deno, and Node.js?
I'm skeptical about stackblitz claims. The last time I checked that is closed source code https://github.com/stackblitz/webcontainer-core/issues/658.
-
Use SSH in browser
StackBlitz claimed https://blog.stackblitz.com/posts/introducing-webcontainers/ to have implemented Node.js in the browser, though I have not observed any evidence of that being true and correct https://github.com/stackblitz/webcontainer-core/issues/658.
- Node.js in Chrome extension
-
Docker Desktop Requires A Paid Subscription, Now What?
The other honorable mention is StackBlitz, a web-based web editor for making containers that run Javascript applications. Interestingly, StackBlitz is championing WebContainers, a technology that allows developers to start NodeJS servers within the browser. The downside is, this technology only works with Javascript-based projects (NodeJS, NextJS, etc). I include it here because WebContainers could easily be extended to support other languages via WASM, like Ruby. I’ll also add in Buildah, a tool for building OCI images. I won’t say much about this tool because it’s designed for building images; you still need another service, like Podman, to actually create the containers.
What are some alternatives?
WASI - WebAssembly System Interface
wasmer - 🚀 The leading Wasm Runtime supporting WASIX, WASI and Emscripten
onload - OpenOnload high performance user-level network stack
standards-positions
Uno Platform - Build Mobile, Desktop and WebAssembly apps with C# and XAML. Today. Open source and professionally supported.
wasm-clang - Running Clang/LLD in WebAssembly Demo
function-references - Proposal for Typed Function References
joystick - A full-stack JavaScript framework for building stable, easy-to-maintain apps and websites.
gc - Branch of the spec repo scoped to discussion of GC integration in WebAssembly
openvscode-server - Run upstream VS Code on a remote machine with access through a modern web browser from any device, anywhere.
jupyterlite - Wasm powered Jupyter running in the browser 💡
biwascheme - Scheme interpreter written in JavaScript