fvim VS Avalonia.FuncUI

fvim and goneovim have support for gui-widgets.nvim which is a sort of protocol to define images and let Neovim GUIs display them.

fvim has a cool idea of having a common protocol for ui extensions: https://github.com/yatli/gui-widgets.nvim

While there is Avalonia.FuncUI you can use Avalonia with only F#/Xaml as well, take https://github.com/yatli/fvim as an example it's an avalonia app and doesn't use the FuncUI DSL but you'll have to handle your views in an OOP'ish way

I use fvim to meet the use case you describe. I love it.

For those interested in .NET languages with alternative compilation targets, Elmish (https://elmish.github.io/elmish/) is pretty unique.

We use F# on the front end (instead of TS), and thanks to the Fable compiler (which transpiles F# to JS, Python, Dart, PHP and Rust), most of the benefits of an Elm-style model in the UI can be ported to all sorts of different outputs languages. The rust target is in beta, but its promising because the WASM bundle size stands to be dramatically lower.

While the default is reactivity library for Elmish is React, you can swap in Avalonia/FuncUI (https://github.com/fsprojects/Avalonia.FuncUI) pretty easily as well.

The code to declare/build the widgets is quite nice. Modifying widgets by hand on certain signals or manually re-wiring all the signals seems a bit outdated to me.

Wonder if something like FuncUI [1] could be built on top of it.

[1] https://github.com/fsprojects/Avalonia.FuncUI

OTOH, if desktop really is the primary focus, and if you can drop the idea of reusable UI code, then Avalonia is a great choice for F# as you can use a Avalonia.FuncUI and/or Elmish.Avalonia.

And one more MVU for you https://github.com/fsprojects/Avalonia.FuncUI

You might want to check out Avalonia.FuncUI, which lets you use F# and the cross-platform Avalonia framework to build desktop applications with an Elm-like architecture: https://github.com/fsprojects/Avalonia.FuncUI#example-using-...