threads
biwascheme
Our great sponsors
threads | biwascheme | |
---|---|---|
16 | 16 | |
668 | 723 | |
2.7% | 0.7% | |
2.0 | 8.4 | |
4 months ago | 4 days ago | |
WebAssembly | JavaScript | |
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.
biwascheme
-
Embeddable Common Lisp 23.9.9
If Scheme is something you enjoy, BiwaScheme's interpreter can be instantiated from within Javascript and can be used to evaluate Scheme code.
https://www.biwascheme.org/
- BiwaScheme is a Scheme interpreter written in JavaScript
-
Directly compiling Scheme to WebAssembly: lambdas, recursion, iteration
This project is very exciting. In the meantime, there are a couple of options:
BiwaScheme: https://www.biwascheme.org/
Advantages: written in JavaScript, with excellent JS interop. Project has some history.
Disadvantages: slower than S7 (though still plenty fast for many uses), less-complete (e.g., no syntax-rules or syntax-case, though it does have its own define-macro).
S7 Scheme: https://cm-gitlab.stanford.edu/bil/s7
Written in C, but can be transpiled to WASM (see https://github.com/actonDev/s7-playground/ )
Advantages: This project also has some history. Considerably faster than BiwaScheme.
Disadvantages: JS interop is clumsier (basically the same issues as JS interop with any WASM code... this could probably be mitigated considerably if someone wanted to take the time).
-
All Web frontend lisp projects
For Scheme implementations there are LIPS and biwascheme. I haven't done more than play around with them, so I can't really give an informed opinion about pros and cons or favorites.
-
My reading workflow (you guys might find some bits from it useful)
I used to have hundreds of open tabs. From there I kept repurposing it to do more stuff with the browser until it reached its current state, where I want to make it a "extend firefox from Emacs" thing. It kinda do that already, but extending the firefox-extension itself require the extension to be re-built (so you need whole javascript tooling, rebuild and reload the addon etc). I am considering adding something like biwascheme to it soon to work around that.
-
The stepmotherly treatment of Windows platform by Scheme implementors
And then users can just use biwascheme and run programs in mainframes and their smart toasters
-
If you were hired to create a new distribution of Lisp, what would you include?
Languages like Biwa Scheme and LIPS Scheme are good for running Scheme in the browser. But I would prefer compiling Scheme code to JavaScript in the server, then serving the compiled JavaScript image to the browser.
-
LIPS Scheme version 1.0.0-beta.15 is out
Just a note that even BiwaScheme doesn't fully implement call/cc, it doesn't save the whole environment when capturing.
Very cool! Do you know how this compares with Biwascheme? https://www.biwascheme.org/
-
Racketscript/Racketscript: Racket to JavaScript Compiler
Biwascheme has some weird scoping bugs that makes me a litte afraid of using it for serious stuff. It seems nixe and all, but this: https://github.com/biwascheme/biwascheme/issues/125 is not very confidemce inspiring.
There is another schemey language that compiles to JS that accepts things like this:
(when (start-are-aligned?)
What are some alternatives?
WASI - WebAssembly System Interface
LIPS - Scheme based powerful lisp interpreter in JavaScript
webcontainer-core - Dev environments. In your web app.
gambit - Gambit is an efficient implementation of the Scheme programming language.
onload - OpenOnload high performance user-level network stack
schism - A self-hosting Scheme to WebAssembly compiler
Uno Platform - Build Mobile, Desktop and WebAssembly apps with C# and XAML. Today. Open source and professionally supported.
function-references - Proposal for Typed Function References
racketscript - Racket to JavaScript Compiler
gc - Branch of the spec repo scoped to discussion of GC integration in WebAssembly
reference-types - Proposal for adding basic reference types (anyref)