Conversation

Notices

1. Embed this notice
   dave (dthompson@toot.cat)'s status on Sunday, 19-Jan-2025 03:25:25 JST dave

   wrote a quick post about the problems I've experienced with wasm gc and realtime graphics https://dthompson.us/posts/wasm-gc-isnt-ready-for-realtime-graphics.html

   • Embed this notice
     David Wilson (daviwil@fosstodon.org)'s status on Sunday, 19-Jan-2025 03:45:59 JST David Wilson

     in reply to

     @dthompson damn, that's unfortunate :/

   • Embed this notice
     Arne Babenhauserheide (arnebab@rollenspiel.social)'s status on Sunday, 19-Jan-2025 05:07:11 JST Arne Babenhauserheide

     in reply to

     @dthompson the scratch space option sounds a bit like the bytearray trick you use in Guile+SDL code to avoid GC pressure.

     (or did I get that wrong?)

   • Embed this notice
     dave (dthompson@toot.cat)'s status on Sunday, 19-Jan-2025 06:13:14 JST dave

     in reply to

     • Arne Babenhauserheide

     @ArneBab on guile you can access the contents of a foreign pointer as a bytevector directly, no copy required.

   • Embed this notice
     dave (dthompson@toot.cat)'s status on Sunday, 19-Jan-2025 06:14:34 JST dave

     in reply to

     • Vivien

     @gugurumbe not part of the public interface. hoot's implementation uses a memory object as stack space for unboxed values, though.

   • Embed this notice
     Vivien (gugurumbe@mastouille.fr)'s status on Sunday, 19-Jan-2025 06:14:36 JST Vivien

     in reply to

     @dthompson I was wondering if there was a way to access the linear memory with Hoot. Do you happen to know if it is possible?

   • Embed this notice
     dave (dthompson@toot.cat)'s status on Sunday, 19-Jan-2025 06:15:17 JST dave

     in reply to

     • David Wilson

     @daviwil yeah, I've known this for awhile and have had enough people ask me about webgl on hoot that I figured I should finally write this up.

   • Embed this notice
     dave (dthompson@toot.cat)'s status on Sunday, 19-Jan-2025 20:41:38 JST dave

     in reply to

     one mistake I made is that saying wasm GC is wonderful wasn't enough to keep the anti GC crowd from saying that no GC managed runtime can do realtime graphics, which is total bullshit btw!

   • Embed this notice
     Arne Babenhauserheide (arnebab@rollenspiel.social)'s status on Sunday, 19-Jan-2025 20:56:30 JST Arne Babenhauserheide

     in reply to

     @dthompson so it’s more similar to batching in Chickadee where you prepare images that are then only referenced, cropped and moved?

   • Embed this notice
     dave (dthompson@toot.cat)'s status on Sunday, 19-Jan-2025 22:54:59 JST dave

     in reply to

     • Arne Babenhauserheide

     @ArneBab batching is for the geometry not the image data and that's useful for lots of data that changes every frame. Batching would be very painful to do with wasm GC right now due to the problems mentioned in the blog post. These problems don't exist in Guile.

   • Embed this notice
     Arne Babenhauserheide (arnebab@rollenspiel.social)'s status on Monday, 20-Jan-2025 01:35:30 JST Arne Babenhauserheide

     in reply to

     @dthompson Then I misunderstood what you meant with the scratch space. Isn’t that something where you prepare data by pushing it through the wasm-gc/wasm-linar-space boundary?