AutoLISP interpreter in Rust/WASM – a CAD workflow invented 33 yrs ago
https://acadlisp.de/noscript.html
#HackerNews #AutoLISP #Rust #WASM #CAD #Workflow #Innovation
Rust/WASM lighting data toolkit – parses legacy formats, generates SVGs
GenresFox – Open-source, customizable new tab page extension in WASM
https://github.com/zayokami/GenresFox
#HackerNews #GenresFox #OpenSource #WASM #NewTabExtension #Customizable
#ai #wasm
So.. was researching wasm stuff and discovered MoonBit. A language /tool chain / cloud platform? focused on creating wasm outputs.
Looking at the features on the scream sheet page, and wham AI... Built in. A core feature of the platform and it's editors.
Ok, hard pass.
Why the hell are people so against actually knowing and learning how the code works? (This includes learning how it doesn't work and the errors to expect. Solving the problems that come up is part of understanding the creations you make. Being able to answer "why" something was coded one way and not another. The AI things being pushed on us, can't answer that. Or if they claim to... Trust that it's bullshit.)
🫧 socialcoding..
boosted
A short introductory blog post about Fruits & Tails, our little video game.
#WASM / #WASI based #plugin architectures vs #AGPL?
I assume this is valid, but #IANAL and unsure if it is indeed the case:
- If the core system is AGPL-licensed and integrates a Wasm WASI runtime.
- Then 3rd-party WASI Components can have different licenses.
- Esp. when they are downloaded and installed at run-time.
OTOH perhaps not.. and it depends on who designed the #WIT #RPC interface, and what its #license is.
#Socialcoding topic (2024, all fedi links rotted)..
https://discuss.coding.social/t/sx-licensing-of-plugin-architecture-vs-agpl/506
A short introductory blog post about Fruits & Tails, our little video game.
Arborium: Tree-sitter code highlighting with Native and WASM targets
#HackerNews #Arborium #Tree-sitter #WASM #Native #CodeHighlighting
devSJR :python: :rstats:
boosted
Between 1988 and 1995 Jack Crenshaw posted on Usenet "Let's Build a Compiler", a tutorial series on writing a Pascal compiler that generates 68K Assembly. 35 years later Eli Bendersky revisited the series and rewrote the compiler in Python to generate WebAssembly.
https://eli.thegreenplace.net/2025/revisiting-lets-build-a-compiler
Between 1988 and 1995 Jack Crenshaw posted on Usenet "Let's Build a Compiler", a tutorial series on writing a Pascal compiler that generates 68K Assembly. 35 years later Eli Bendersky revisited the series and rewrote the compiler in Python to generate WebAssembly.
https://eli.thegreenplace.net/2025/revisiting-lets-build-a-compiler
Epsilon: A WASM virtual machine written in Go
https://github.com/ziggy42/epsilon
#HackerNews #Epsilon #WASM #Go #VirtualMachine #ProgrammingTechnology #OpenSource
Konrad Hinsen
and 1 other
boosted
TurtleWare: Common Lisp and WebAssembly https://turtleware.eu/posts/Common-Lisp-and-WebAssembly.html
Ghostty compiled to WASM with xterm.js API compatibility
https://github.com/coder/ghostty-web
#HackerNews #Ghostty #WASM #xterm.js #API #compatibility #web #development
Konrad Hinsen
and 1 other
boosted
I wrote a blog post, I wrote a blog post! enjoy :)
https://turtleware.eu/posts/Common-Lisp-and-WebAssembly.html
TurtleWare: Common Lisp and WebAssembly https://turtleware.eu/posts/Common-Lisp-and-WebAssembly.html
I wrote a blog post, I wrote a blog post! enjoy :)
https://turtleware.eu/posts/Common-Lisp-and-WebAssembly.html
Giacomo Leidi
and 1 other
boosted
#spritely #hoot in a toot: how to deploy #Guile #Scheme as static website via #webassembly (complete #Wisp example).
The code from the two attached images, as written, runs on
https://www.draketo.de/software/hoot.html
Try it out!
It’s two pages from Naming & Logic: Programming Essentials with Wisp.
printed: https://www.epubli.com/shop/naming-and-logic-programming-essentials-with-wisp-9783565093199
website: https://www.draketo.de/software/programming-basics-wisp
This adds parallel fetches (do you see where?). If you adopt it, ensure that your server compresses application/wasm.
Load your interface (includes startup time optimizations):
#+begin_src js :tangle hoot.js
/* file: hoot.js */
var f = window.fetch; window.fetch = (inp, ini) => f(inp,
{credentials: 'include', mode: 'no-cors', ...ini});
window.addEventListener("load", () =>
fetch("hoot.wasm")
.then(r => r.arrayBuffer())
.then(bytes => Scheme.load_main(bytes, {
user_imports: { // mapped via define-foreign
document: {
body() { return document.body; },
createTextNode: Document.prototype
.createTextNode.bind(document)
},
element: {
appendChild(parent, child) {
return parent.appendChild(child);}}}})));
#+end_src
Include =reflect.js= and =hoot.js= from a HTML page:
#+begin_src html :tangle hoot.html
<!DOCTYPE html> <!-- file: hoot.html -->
<html><head><title>Hello Hoot</title>
<script type="text/javascript" src="reflect.js"></script>
<script type="text/javascript" src="hoot.js"></script>
<link rel="preload" as="fetch" href="hoot.wasm"></link>
<link rel="preload" as="fetch" href="wtf8.wasm"></link>
<link rel="preload" as="fetch" href="reflect.wasm"></link>
</head><body><h1>Hoot Test</h1></body></html>
#+end_src
For local testing, hoot provides a minimal webserver:
#+begin_src bash
guix shell guile-hoot guile-next -- \
guile -c '((@ (hoot web-server) serve))'
#+end_src
![*Browser again: clientside wasm.* @@html:<a id="deploy-hoot-wasm" name="deploy-hoot-wasm"></a>@@
To run clientside, you can package your project with [[https://spritely.institute/hoot/][Hoot]]: build an interface and compile to wasm:
#+begin_src wisp :results output :tangle hoot.w
;; file: hoot.w
use-modules : hoot ffi ;; guile specific import
;; the interface
define-foreign document-body "document" "body"
. -> (ref null extern)
define-foreign make-text-node "document" "createTextNode"
. (ref string) -> (ref null extern)
define-foreign append-child! "element" "appendChild"
. (ref null extern) (ref null extern)
. -> (ref null extern)
;; your code
append-child! : document-body
make-text-node "Hello, world!"
#+end_src
Transpile with =wisp2lisp= and =guild compile-wasm=. If you run Guix:
#+begin_src bash
guix shell guile guile-wisp -- \
wisp2lisp hoot.w > hoot.scm && \
guix shell guile-hoot guile-next -- \
guild compile-wasm -o hoot.wasm hoot.scm
#+end_src
Get reflection tools from Guile Hoot (licensed Apache 2.0) with Guix:
#+latex: \ThisLLCornerWallPaper{0.26}{programming-scheme-hoot}%
#+begin_src bash
guix shell guile-hoot guile-next -- bash -c \
'cp $GUIX_ENVIRONMENT/share/*hoot/*/re*/{*.js,*.wasm} ./'
#+end_src](https://rollenspiel.social/system/media_attachments/files/115/571/874/352/976/810/original/461d1bbc2af3da4c.png)
*Browser again: clientside wasm.* @@html:<a id="deploy-hoot-wasm" name="deploy-hoot-wasm"></a>@@
To run clientside, you can package your project with [[https://spritely.institute/hoot/][Hoot]]: build an interface and compile to wasm:
#+begin_src wisp :results output :tangle hoot.w
;; file: hoot.w
use-modules : hoot ffi ;; guile specific import
;; the interface
define-foreign document-body "document" "body"
. -> (ref null extern)
define-foreign make-text-node "document" "createTextNode"
. (ref string) -> (ref null extern)
define-foreign append-child! "element" "appendChild"
. (ref null extern) (ref null extern)
. -> (ref null extern)
;; your code
append-child! : document-body
make-text-node "Hello, world!"
#+end_src
Transpile with =wisp2lisp= and =guild compile-wasm=. If you run Guix:
#+begin_src bash
guix shell guile guile-wisp -- \
wisp2lisp hoot.w > hoot.scm && \
guix shell guile-hoot guile-next -- \
guild compile-wasm -o hoot.wasm hoot.scm
#+end_src
Get reflection tools from Guile Hoot (licensed Apache 2.0) with Guix:
#+latex: \ThisLLCornerWallPaper{0.26}{programming-scheme-hoot}%
#+begin_src bash
guix shell guile-hoot guile-next -- bash -c \
'cp $GUIX_ENVIRONMENT/share/*hoot/*/re*/{*.js,*.wasm} ./'
#+end_src