Since doing the Zig Native Messaging host with help from folks here (since y’all don’t like anything labeled “AI” or “LLM”) Porting handwritten JavaScript to Zig: Native Messaging host - #19 by TerenceTux, GitHub - guest271314/native-messaging-zig: Zig Native Messaging host · GitHub, I’ve been working on AOT JavaScript to WASM GC with js2wasm GitHub - loopdive/js2: ECMAScript to WebAssembly GC AOT compiler · GitHub, GitHub - guest271314/native-messaging-js2wasm: js2wasm Native Messaging host · GitHub; testing ComponentizeJS, jco, componentize-qjs GitHub - guest271314/native-messaging-componentize-js: ComponentizeJS Native Messaging host · GitHub, GitHub - guest271314/native-messaging-componentize-qjs: componentize-qjs Native Messaging host · GitHub; compiling QuickJS NG to WASM with WASI support, with my JavaScript pre-embedded, and optimizing that output for size How to optimize WASM build · quickjs-ng/quickjs · Discussion #1546 · GitHub; compiling Bellard and Gordon’s Micro QuickJS to WASM, same as above, with JavaScript -re-embedded, and optimizing WASM binary for size (down to around 239.5 KiB right now, still W.I.P.); implementing a Native Messaging host in D, with WASM and WASI support (still testing, unpublished, though I’ll probably throw on the GitHub (more non-Zig domain) sometime this week); revisting non-containerized live media streaming and static playback re a new IETF proposal for a “container” for WebCodecs involved media draft-ietf-moq-loc-02 - Low Overhead Media Container - kinda the opposite of why WebCodecs came about API for containers? · Issue #24 · w3c/webcodecs · GitHub, in conjunction with my implementation of stacking media produced by WebCodecs into a blob WebCodecsOpusRecorder/WebCodecsOpusRecorder.js at main · guest271314/WebCodecsOpusRecorder · GitHub, with separate indexing to track offsets, and thinking about how to even do that without offsets, more too thinking about exactly what a media “container” is and isn’t - per some consensus, 'cause a codec itself could be considered a media container.
Getting banned from Bytecode Alliance Banned from Bytecode Alliance Zulip (and banning you from engaging in our GitHub repos going forward) · Issue #46 · guest271314/banned · GitHub for daring to scrutinize the technical issues with using StarlingMonkey for the WebAssembly Component Model implementations where the base WASM binary spit out is around 13.4 MiB! Whereas QuickJS can be used to produce a WASM binary under 1 MiB. Thus my independent experiments with QuickJS NG and Micro QuickJS to get that size down further.
A lot of hand digging for some concrete footing and eventual 10 foot plus walls at a French/Victorian type chateau stylee job. Searing in my brain you HAVE to put some steel on it when it’s a sand finish. More hand digging at other jobs for sidewalks and stuff.
Thinking about JavaScript source static analysis to determine exactly what is necessary to complete the instruction using a given engine, and extracting ONLY that source code to build custom engines/runtimes.
Etc.