Silk.NET VS ReactiveUI

Genuine curiosity - what would be your motivation to use Java over C# here aside from familiarity (which is perfectly understandable)? The latter takes heavy focus on making sure to provide features like structs and pointers with little to no friction, you can even AOT compile it and statically link SDL2 into a single executable.

But either way, if you want to try it out, then all it needs is

- SDK from https://dot.net/download (or package manager of your choice if you are on Linux e.g. `sudo apt-get install dotnet-sdk-8.0`, !do not! use Homebrew if you are on macOS however, use .pkg installer)

- C# extension for VS Code (DevKit is not needed)

- SDL2 bindings: https://github.com/dotnet/Silk.NET

A couple other options than what has been suggested so far: - TerraFX.Interop.Windows. Raw, blittable, 1:1 bindings for all Win32, D2D/D3D11/D3D12 APIs (there's also a version with Vulkan bindings). As close to doing #include as you can get in C#. This is my personal favorite, I use it in my own ComputeSharp library, and transitively we use it in the Microsoft Store too 🙂 - Silk.NET another version of high-performance bindings, more opinionated than TerraFX and with some additional helpers to make it a bit easier to use.

Here is an example of using "releases" in GitHub: https://github.com/dotnet/Silk.NET/releases. Most repositories use releases and releases seem like they wpuld be appropriate for your repository too.

I've been looking at this. Is this similar to the UrhoSharp project you talk about? https://github.com/dotnet/Silk.NET

Have you looked at Silk.NET before?

Take a look at https://github.com/dotnet/Silk.NET . You should be able to use your existing rendering context with it. So you could use something like imgui (They have bindings for that) to render your UI. Or if you just start writing your rendering code, you could consider writing the whole rendering engine with it. I used it in the past for a game engine and performance is no problem for most of the usecases.

ReactiveUI Official Website: For information on ReactiveUI, which closely integrates with DynamicData, visit the official website. This site offers extensive documentation and tutorials for both ReactiveUI and DynamicData. ReactiveUI.

ReactiveUI is based on Rx and very popular in the .Net world: https://www.reactiveui.net/.

I use PropertyChanged.Fody all the time and it works fantastically and consistently for implementing INotifyPropertyChange. It is even smart enough to understand dependencies within your get/set functions (should you choose to have custom ones) and notify that property if any of it's dependent properties change. While we are on the subject, if you are using MVVM with observables, you should really check out ReactiveUI. It is wonderful.

Personally I learned to use rx and observables by starting to use ReactiveUI combined with DynamicData for my WPF app MVVM architecture. It was maybe not to best choice out there, but I learned to work with it and some things it allows to do is awesome.

My favorite framework is Reactive UI but it's a bit more advanced than most MVVM frameworks since it uses Reactive Programming. You can still try its most basic features, though.

There is a lot of overlap between WPF and Avalonia so I would start with either one of those. Most certainly Avalonia if you plan to do cross platform dev. I would also highly recommend that you learn and conform to MVVM and dependency injection for your architecture in order to write clean, maintainable, and testable code. My recommendation is ReactiveUI. It leans heavily on more modern patterns like Reactive extensions and IObservable and it can do so much more than just MVVM. As such, it is also very similar to Angular so the concepts will transfer easily if you ever need to do web development. On a side note, Pluralsight has a nice quick course on SOLID design principles. If your code is a mess, it would be a good idea to take a course on this though learning MVVM will be a big step in the right direction.

Also, about data binding and reactivity if you really enjoy WinForms, nevar forget!! https://www.reactiveui.net

Your UI needs to bind to something that can programmatically notify it about changes, we call these things View-Models. Usually View-Models implement INotifyPropertyChanged interface (another key interface is INotifyCollectionChanged that is responsible for notifying collection views that number of items is changed and they need to update the UI accordingly). You can do that (the implementation of the interface) manually or use some library to do that for you just to cut some boilerplate code (e.g. ReactiveUI + Fody or Microsoft.Toolkit.MVVM or maybe even this or this).