
This is a website.
Entirely written in Rust.
Built with Ratzilla ( @ratatui_rs + WebAssembly)
Same code runs in the terminal.
The future is bright.
#Tag
This is a website.
Entirely written in Rust.
Built with Ratzilla ( @ratatui_rs + WebAssembly)
Same code runs in the terminal.
The future is bright.
This is a website.
Entirely written in Rust.
Built with Ratzilla ( @ratatui_rs + WebAssembly)
Same code runs in the terminal.
The future is bright.
I wonder if anybody's writing #WebAssembly by hand yet.
After almost a week of refactoring and experimenting with several different approaches, I've updated my Zig nD SIMD vector library to be compatible with the latest Zig 0.15.1, and at the same time cleaned up some internals.
The solution I settled on is a mix of techniques proposed by others, and was needed due to the removal of the struct/namespace-merging syntax in the new Zig version, which this library heavily relies on. I don't like that the new source code is now more than 2x larger and involves a huge amount of duplication to address the many special cases of supported operations for different vector sizes and types. I might still take another pass to eliminate those (by using @compileError()
for unsupported cases), but that'd be an implementation detail downstream users don't have to care about. I tried AOT code generation as well, but the special case handling made this feel less maintainable...
UPDATE: The only breaking change is the handling of vector swizzles. I had to remove the hundreds of named swizzle functions and replaced them with a single (comptime optimized) .swizzle(vec, pattern)
, e.g. .swizzle(vec, "xxyy")
...
If you're interested, the new code is here:
https://github.com/thi-ng/zig-thing/blob/main/src/vectors.zig
The readme contains details about the many supported operations:
https://github.com/thi-ng/zig-thing/blob/main/doc/vectors.md
Installation instructions in the main repo readme:
https://github.com/thi-ng/zig-thing/tree/main
Btw. It's amazing that this swizzle function gets compiled into single WASM i8x16.shuffle
ops (per 4 vector components, i.e. swizzling into an 8-dimensional vector would require 2 shuffles):
News includes a new SQL #analytics library called Lotus, plus an interview with Mateusz Front about the Popcorn project enabling Elixir to run in #WebAssembly in the browser! #ElxirLanghttps://www.youtube.com/watch?v=-85KlStS1tc
Yesterday I released new versions of https://thi.ng/wasm-api (and its add-on packages), a modular and extensible bridge API & toolchain for hybrid JS/TS/Zig/WebAssembly apps, now updated to be compatible with the latest Zig version 0.15.1...
The update addresses some of Zig's breaking syntax & build system changes only, nothing on the JS/TS side has changed. As a result https://thi.ng/wasm-api-dom has a slightly revised internal structure (also a breaking change, but nothing major & unavoidable). All bundled Zig examples[1] in the repo have been updated too, take a look for reference (if needed).
FYI More details about the Zig language changes here:
https://ziglang.org/download/0.15.1/release-notes.html#Language-Changes
Specifically, the removal of usingnamespace
has had a major impact on the existing handling of generated types in these wasm-api support packages (or your own) and now forces an additional level of hierarchy in terms of namespacing. This is because usingnamespace
enabled a form of namespace merging, which allowed the generated WASM⭤TS interop types (written to their own sourcefile) to be merged/hoisted into the main library module.
For example, previously after importing const dom = @import("wasm-api-dom");
we could refer to a type via dom.WindowInfo
. Now with namespace merging removed, we have to use dom.types.WindowInfo
. As I said, it's not a major departure, but a breaking change nonetheless[2]...
The build.zig
file bundled with https://thi.ng/wasm-api is now also only compatible with Zig 0.15.1 (for now). Build files for older Zig versions are still included too (in the same directory)[3].
Lastly, once more for the record: The wasm-api bridge itself is NOT tied to Zig (or a particular version), however it's the main use case/language for my own WebAssembly use cases...
[1] https://github.com/thi-ng/umbrella/tree/develop/examples (all examples starting with zig-*
)
[2] The existing design of these modules helped to keep these breaking changes to a minimum in userland code and these updates are all following the same uniform pattern (i.e. exposing interop types via modulename.types.TypeName
...)
[3] https://github.com/thi-ng/umbrella/tree/develop/packages/wasm-api#using-the-zig-build-system
#ThingUmbrella#Zig#Ziglang#WebAssembly#WASM#TypeScript#JavaScript#Interop
Yesterday I released new versions of https://thi.ng/wasm-api (and its add-on packages), a modular and extensible bridge API & toolchain for hybrid JS/TS/Zig/WebAssembly apps, now updated to be compatible with the latest Zig version 0.15.1...
The update addresses some of Zig's breaking syntax & build system changes only, nothing on the JS/TS side has changed. As a result https://thi.ng/wasm-api-dom has a slightly revised internal structure (also a breaking change, but nothing major & unavoidable). All bundled Zig examples[1] in the repo have been updated too, take a look for reference (if needed).
FYI More details about the Zig language changes here:
https://ziglang.org/download/0.15.1/release-notes.html#Language-Changes
Specifically, the removal of usingnamespace
has had a major impact on the existing handling of generated types in these wasm-api support packages (or your own) and now forces an additional level of hierarchy in terms of namespacing. This is because usingnamespace
enabled a form of namespace merging, which allowed the generated WASM⭤TS interop types (written to their own sourcefile) to be merged/hoisted into the main library module.
For example, previously after importing const dom = @import("wasm-api-dom");
we could refer to a type via dom.WindowInfo
. Now with namespace merging removed, we have to use dom.types.WindowInfo
. As I said, it's not a major departure, but a breaking change nonetheless[2]...
The build.zig
file bundled with https://thi.ng/wasm-api is now also only compatible with Zig 0.15.1 (for now). Build files for older Zig versions are still included too (in the same directory)[3].
Lastly, once more for the record: The wasm-api bridge itself is NOT tied to Zig (or a particular version), however it's the main use case/language for my own WebAssembly use cases...
[1] https://github.com/thi-ng/umbrella/tree/develop/examples (all examples starting with zig-*
)
[2] The existing design of these modules helped to keep these breaking changes to a minimum in userland code and these updates are all following the same uniform pattern (i.e. exposing interop types via modulename.types.TypeName
...)
[3] https://github.com/thi-ng/umbrella/tree/develop/packages/wasm-api#using-the-zig-build-system
#ThingUmbrella#Zig#Ziglang#WebAssembly#WASM#TypeScript#JavaScript#Interop
I wrote a blog post that summarizes the current progress on Web Embeddable Common Lisp:
https://turtleware.eu/posts/Using-Common-Lisp-from-inside-the-Browser.html
This work is possible thanks to funding from @nlnet via @NGIZero program.
I wrote a blog post that summarizes the current progress on Web Embeddable Common Lisp:
https://turtleware.eu/posts/Using-Common-Lisp-from-inside-the-Browser.html
This work is possible thanks to funding from @nlnet via @NGIZero program.
If anyone's interested in a #webassembly meetup kinda thing prior to #osssummit EU Sunday evening the 24th of August, I'll be hosting one there in AMS.
Looking for a nice place as we speak....
If anyone's interested in a #webassembly meetup kinda thing prior to #osssummit EU Sunday evening the 24th of August, I'll be hosting one there in AMS.
Looking for a nice place as we speak....
News includes Phoenix v1.8 shipping with AGENTS support, Popcorn bringing Elixir to the browser via #WebAssembly, LiveVue v0.6.0 with major performance improvements, and more! #ElixirLang@elixirlang@elixirphoenix#AIhttps://www.youtube.com/watch?v=8hMcN-WLp7I
WebAssembly: Yes, but for What?, by @wingo (@acmqueue.bsky.social):
WebAssembly: Yes, but for What?, by @wingo (@acmqueue.bsky.social):
Damn... Rust devs going crazy with these libraries.
⚒️ sledgehammer_bindgen 🦀
💥 Breaking the performance barrier of WASM/JS communication.
⚡ Faster Rust batched bindings for JS code.
⭐ GitHub: https://github.com/ealmloff/sledgehammer_bindgen
#rustlang #webassembly #wasm #javascript #performance #bindings #frontend #bindgen
A space for Bonfire maintainers and contributors to communicate