OpenSceneGraph VS Skia

I started in 2001 with OpenSceneGraph which made extensive use of intrusive pointers. This was 10 years before C++11 note. That codebase continues to be relevant and as performing as ever.

I have been using OpenSceneGraph for over 20 years. It is used in the military a lot and I myself have seen it used to simulate war scenarios with realtime data aboard of a command-and-control center of a battleship.

Does http://www.openscenegraph.org/ fit?

Speed Dreams: It is a fork of TORCS, and was born as the need to include many more functions to the latter. In Speed Dreams the menus would be completely redesigned, adding many more options and making them much more intuitive; the game acquired dynamic time, improvements in reflections, career mode, a new simulation mode and multi threading. Over time many more options were implemented, such as local multiplayer mode, Force Feedback, and of course more and better cars and tracks, a new and more powerfull graphic engine (OpenSceneGraph) among other things, making it a much more complete game than its predecessor. They recently they have presented version 2.2.3. You can also install it in AppImage and Flatpak format.

openscenegraph (mainly focuses on graphics, used by openmw for example)

I love Godot for a complete game engine. For just the renderer you could consider http://www.openscenegraph.org

-Finish the implementation of the new OpenSceneGraph rendering engine: The game allows to replace the default renderer (ssggraph) with OpenSceneGraph, but it still needs to implement many features to be completed, as well as further optimisation.

There’s also Skia by Google. Used by Android and Google Chrome.

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/