Frühere Suchanfragen
Suchoptionen
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
@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?)
@ArneBab on guile you can access the contents of a foreign pointer as a bytevector directly, no copy required.
@dthompson so it’s more similar to batching in Chickadee where you prepare images that are then only referenced, cropped and moved?
@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.
@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?