Skia VS bgfx

Not specially something that you cannot do without WASM but at $WORK we are using a WASM build of Skia [0] to render canvas from nodejs.

Why use WASM ? Because we wanted to stay close to our stack (ie. calling wasm from nodejs). Do it work ? Yes, memory consumption is quite heavy though (each WASM module have its own heap that can quickly grow).

However we are looking to directly use Skia now and avoid the overhead of WASM so i think its a nice solution in the beginning but you might want to ditch it later on.

[0]: https://github.com/google/skia/tree/main/modules/canvaskit

I use SkVx from Skia. It uses compilers' vector extensions and few platform-specific intrinsics. If no vector extension available (e.g. msvc), a scalar implementation is provided in the hope that compiler can vectorize it.

Regarding compiling to JS, you can compile dart to JS however when running Flutter on mobile platforms such as iOS or Android, you're not compiling to JS but instead you're using Dart to draw widgets on the screen via Flutter engine which uses a cross-platform graphics engine under the hood called Skia. If you're running on web on the other hand, your dart code would compile to vector graphics rendered within a canvas element in pure HTML.

It built on a render framework named skia, JetBrains create a kotlin mapping which named skiko for it.

Flutter applications are written in the Dart programming language, and can connect to platform languages such as Java, Kotlin, Swift, and Objective-C. Also, thanks to ffi support, it is possible to interact with the C code directly . Flutter itself is built with C, C++, Dart, and Skia (a 2D rendering engine).

Fleet does not use Compose, but it does use Skiko[1], which also provides binding for Skia[2] (the native graphics library also used by Chrome & Flutter).

The main difference between the libraries is that Skija provides Java/JVM bindings for Skia, whereas Skiko provides Kotlin bindings for Kotlin/JVM, Kotlin/JS, and Kotlin/Native targets. Of course Skiko's Kotlin/JVM bindings can be used with other JVM languages, not just with Kotlin.

[1] https://github.com/JetBrains/skiko

[2] https://skia.org/

RN Skia: https://github.com/Shopify/react-native-skia Skia itself: https://skia.org/

Yeahp, it renders the controls itself using skiasharp, which I believe uses skia

If you want CPU rendering perhaps tiny-skia meets your needs? Also proper Skia is generally the Cairo alternative, though I dunno that its any easier to use or compile than Cairo is. Alternatively you could try Raqote or Piet.

First step: Read the documentation. I see at the bottom of the github page that there's a link, so I go there: https://skia.org/

If you want juste a renderer, you can use BGFX, there is a zig binding that is not a third party.

Take a look at BGFX, sounds like its what you want. Its a cross platform graphics API that is low level like metal or opengl, however it treats opengl, metal, vulkan, etc as backends that u can compile to so you can write your code once and then compile to macos using metal as the backend, compile to web using webgl as the backend, compile for windows using directx as the backend etc etc. Its written in C++ but it has officially supported C bindings so you can use it with C no problem.

bgfx:https://github.com/bkaradzic/bgfx

BGFX

You can have a look at https://github.com/bkaradzic/bgfx

There are still things like BGFX in active development and use. I think the bigger issue is that folks can never really agree on how things should be abstracted for a higher level API.

u/LtJax already mentioned the Sokol library, another somewhat popular cross-platform rendering library is bgfx.

Maybe this

BGFX - Wrapper around low level rendering libraries