home.social

#wazero — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #wazero, aggregated by home.social.

fetched live
  1. So I needed a WebP encoder for a Go project where I had #CGO disabled. I found there is an option using #libwebp compiled to #wasm running on #wazero, but that's pretty slow and uses lots of memory.

    So I made a pure #GoLang encoder, ported from a Rust encoder then optimized: github.com/SeriousBug/webp-go-

    I managed to get better performance than the WASM version! Both encoding speed and memory use, although compression rate and quality is a bit worse.

    #webdev #webp

  2. So I needed a WebP encoder for a Go project where I had disabled. I found there is an option using compiled to running on , but that's pretty slow and uses lots of memory.

    So I made a pure encoder, ported from a Rust encoder then optimized: github.com/SeriousBug/webp-go-

    I managed to get better performance than the WASM version! Both encoding speed and memory use, although compression rate and quality is a bit worse.

  3. So I needed a WebP encoder for a Go project where I had #CGO disabled. I found there is an option using #libwebp compiled to #wasm running on #wazero, but that's pretty slow and uses lots of memory.

    So I made a pure #GoLang encoder, ported from a Rust encoder then optimized: github.com/SeriousBug/webp-go-

    I managed to get better performance than the WASM version! Both encoding speed and memory use, although compression rate and quality is a bit worse.

    #webdev #webp

  4. So I needed a WebP encoder for a Go project where I had #CGO disabled. I found there is an option using #libwebp compiled to #wasm running on #wazero, but that's pretty slow and uses lots of memory.

    So I made a pure #GoLang encoder, ported from a Rust encoder then optimized: github.com/SeriousBug/webp-go-

    I managed to get better performance than the WASM version! Both encoding speed and memory use, although compression rate and quality is a bit worse.

    #webdev #webp

  5. So I needed a WebP encoder for a Go project where I had #CGO disabled. I found there is an option using #libwebp compiled to #wasm running on #wazero, but that's pretty slow and uses lots of memory.

    So I made a pure #GoLang encoder, ported from a Rust encoder then optimized: github.com/SeriousBug/webp-go-

    I managed to get better performance than the WASM version! Both encoding speed and memory use, although compression rate and quality is a bit worse.

    #webdev #webp

  6. Morning activity accompanied by coffee - just building a gotosocial binary without Wazero so it runs on my (very) old thinkpad. #GoToSocial #wazero #ThinkPad #Ubuntu

  7. Morning activity accompanied by coffee - just building a gotosocial binary without Wazero so it runs on my (very) old thinkpad. #GoToSocial #wazero #ThinkPad #Ubuntu

  8. Morning activity accompanied by coffee - just building a gotosocial binary without Wazero so it runs on my (very) old thinkpad. #GoToSocial #wazero #ThinkPad #Ubuntu

  9. Morning activity accompanied by coffee - just building a gotosocial binary without Wazero so it runs on my (very) old thinkpad. #GoToSocial #wazero #ThinkPad #Ubuntu

  10. Morning activity accompanied by coffee - just building a gotosocial binary without Wazero so it runs on my (very) old thinkpad. #GoToSocial #wazero #ThinkPad #Ubuntu

  11. we just cut #wazero 1.12.0! your favorite #wasm runtime for #golang now supports more specs than ever! getting closer to WasmGC!

    github.com/wazero/wazero/relea

  12. we just cut #wazero 1.12.0! your favorite #wasm runtime for #golang now supports more specs than ever! getting closer to WasmGC!

    github.com/wazero/wazero/relea

  13. we just cut #wazero 1.12.0! your favorite #wasm runtime for #golang now supports more specs than ever! getting closer to WasmGC!

    github.com/wazero/wazero/relea

  14. we just cut #wazero 1.12.0! your favorite #wasm runtime for #golang now supports more specs than ever! getting closer to WasmGC!

    github.com/wazero/wazero/relea

  15. we just cut #wazero 1.12.0! your favorite #wasm runtime for #golang now supports more specs than ever! getting closer to WasmGC!

    github.com/wazero/wazero/relea

  16. can't believe #Wasm I/O is less than a week away! Andrea Peruffo and I will be there for our session "The State of Zero-Dependency Wasm" with the latest from #wazero and #chicory 🚀

  17. can't believe #Wasm I/O is less than a week away! Andrea Peruffo and I will be there for our session "The State of Zero-Dependency Wasm" with the latest from #wazero and #chicory 🚀

  18. can't believe #Wasm I/O is less than a week away! Andrea Peruffo and I will be there for our session "The State of Zero-Dependency Wasm" with the latest from #wazero and #chicory 🚀

  19. can't believe #Wasm I/O is less than a week away! Andrea Peruffo and I will be there for our session "The State of Zero-Dependency Wasm" with the latest from #wazero and #chicory 🚀

  20. can't believe #Wasm I/O is less than a week away! Andrea Peruffo and I will be there for our session "The State of Zero-Dependency Wasm" with the latest from #wazero and #chicory 🚀

  21. Another thing to be proud of: the tail spec has been merged into the #wazero #wasm runtime. Even though it's relatively simple, it actually took a few weeks to get right in the interpreter and in both backends (arm64 and amd64).

    Thanks @ncruces and @mathetake for the support!

    read more github.com/tetratelabs/wazero/

  22. Another thing to be proud of: the tail spec has been merged into the #wazero #wasm runtime. Even though it's relatively simple, it actually took a few weeks to get right in the interpreter and in both backends (arm64 and amd64).

    Thanks @ncruces and @mathetake for the support!

    read more github.com/tetratelabs/wazero/

  23. Another thing to be proud of: the tail spec has been merged into the #wazero #wasm runtime. Even though it's relatively simple, it actually took a few weeks to get right in the interpreter and in both backends (arm64 and amd64).

    Thanks @ncruces and @mathetake for the support!

    read more github.com/tetratelabs/wazero/

  24. Another thing to be proud of: the tail spec has been merged into the #wazero #wasm runtime. Even though it's relatively simple, it actually took a few weeks to get right in the interpreter and in both backends (arm64 and amd64).

    Thanks @ncruces and @mathetake for the support!

    read more github.com/tetratelabs/wazero/

  25. Another thing to be proud of: the tail spec has been merged into the #wazero #wasm runtime. Even though it's relatively simple, it actually took a few weeks to get right in the interpreter and in both backends (arm64 and amd64).

    Thanks @ncruces and @mathetake for the support!

    read more github.com/tetratelabs/wazero/

  26. Wasm-плагины на Go

    Привет, Хабр! Когда обсуждают расширяемость бэкендов, первым делом вспоминают нативные плагины на C или C++. Дальше обычно всплывают вопросы ABI, совместимости компиляторов, загрузчиков и фразы «а у нас Alpine с musl». В Go исторически был пакет plugin , но его применимость ограничена окружениями и сборкой. В 2025 году картина проще: берем WebAssembly как изолированный байткод, исполняем его прямо из Go и получаем плагинную архитектуру без плясок с динамическими библиотеками. Далее в статье рассмотрим, как создать практичную систему Wasm-плагинов на Go: с изоляцией, таймаутами, контрактом данных и обновлениями на лету. Для рантайма возьмем wazero , потому что он написан на Go и не требует cgo.

    habr.com/ru/companies/otus/art

    #golang #Golang_плагины #WebAssembly_Go #Wasm_плагины #wazero #TinyGo_wasm #Rust_wasm #WASI_preview1 #WASI_preview2 #Go_plugin_package

  27. Wasm-плагины на Go

    Привет, Хабр! Когда обсуждают расширяемость бэкендов, первым делом вспоминают нативные плагины на C или C++. Дальше обычно всплывают вопросы ABI, совместимости компиляторов, загрузчиков и фразы «а у нас Alpine с musl». В Go исторически был пакет plugin , но его применимость ограничена окружениями и сборкой. В 2025 году картина проще: берем WebAssembly как изолированный байткод, исполняем его прямо из Go и получаем плагинную архитектуру без плясок с динамическими библиотеками. Далее в статье рассмотрим, как создать практичную систему Wasm-плагинов на Go: с изоляцией, таймаутами, контрактом данных и обновлениями на лету. Для рантайма возьмем wazero , потому что он написан на Go и не требует cgo.

    habr.com/ru/companies/otus/art

    #golang #Golang_плагины #WebAssembly_Go #Wasm_плагины #wazero #TinyGo_wasm #Rust_wasm #WASI_preview1 #WASI_preview2 #Go_plugin_package

  28. Wasm-плагины на Go

    Привет, Хабр! Когда обсуждают расширяемость бэкендов, первым делом вспоминают нативные плагины на C или C++. Дальше обычно всплывают вопросы ABI, совместимости компиляторов, загрузчиков и фразы «а у нас Alpine с musl». В Go исторически был пакет plugin , но его применимость ограничена окружениями и сборкой. В 2025 году картина проще: берем WebAssembly как изолированный байткод, исполняем его прямо из Go и получаем плагинную архитектуру без плясок с динамическими библиотеками. Далее в статье рассмотрим, как создать практичную систему Wasm-плагинов на Go: с изоляцией, таймаутами, контрактом данных и обновлениями на лету. Для рантайма возьмем wazero , потому что он написан на Go и не требует cgo.

    habr.com/ru/companies/otus/art

    #golang #Golang_плагины #WebAssembly_Go #Wasm_плагины #wazero #TinyGo_wasm #Rust_wasm #WASI_preview1 #WASI_preview2 #Go_plugin_package

  29. Also if you wanna hang the coming week, we're hosting a hackathon in SFO (remote attendance too!) I'll be there too!

    Join us to talk about #Wasm, #MCP, #AI. I myself will be looking forward to chat about #Java, #Chicory #extism and even #Android! (you're interested in #wazero and #Go too? Be my guest) lu.ma/ery1237h

  30. Also if you wanna hang the coming week, we're hosting a hackathon in SFO (remote attendance too!) I'll be there too!

    Join us to talk about #Wasm, #MCP, #AI. I myself will be looking forward to chat about #Java, #Chicory #extism and even #Android! (you're interested in #wazero and #Go too? Be my guest) lu.ma/ery1237h

  31. Also if you wanna hang the coming week, we're hosting a hackathon in SFO (remote attendance too!) I'll be there too!

    Join us to talk about #Wasm, #MCP, #AI. I myself will be looking forward to chat about #Java, #Chicory #extism and even #Android! (you're interested in #wazero and #Go too? Be my guest) lu.ma/ery1237h

  32. Also if you wanna hang the coming week, we're hosting a hackathon in SFO (remote attendance too!) I'll be there too!

    Join us to talk about #Wasm, #MCP, #AI. I myself will be looking forward to chat about #Java, #Chicory #extism and even #Android! (you're interested in #wazero and #Go too? Be my guest) lu.ma/ery1237h

  33. Also if you wanna hang the coming week, we're hosting a hackathon in SFO (remote attendance too!) I'll be there too!

    Join us to talk about #Wasm, #MCP, #AI. I myself will be looking forward to chat about #Java, #Chicory #extism and even #Android! (you're interested in #wazero and #Go too? Be my guest) lu.ma/ery1237h

  34. Cool stuff! Not only is this running #wasm workloads with #wazero on top of an actor system (Hollywood), but it also supports JS by running SpiderMonkey-in-Wasm-on-wazero 🤩
    youtube.com/watch?v=DivENcC7gb

  35. Cool stuff! Not only is this running #wasm workloads with #wazero on top of an actor system (Hollywood), but it also supports JS by running SpiderMonkey-in-Wasm-on-wazero 🤩
    youtube.com/watch?v=DivENcC7gb