That sounded good, until I saw
> Frontends (Svelte Web Components), Desktops (Qt GTK), Runtimes (NodeJS Deno Bun)
It's basically another React/React-Native, though being based on Svelte could have more compile-time smarts.
I'm particularly unimpressed with NodeJS, and something like Flutter/Dart seems a step up from that.
That said, I'm glad it was made and it was probably a great challenge and joy to have made. Congrats! (I'm just not the target audience.)
deno/bun/node will suffice. I just rewrote it to use nodegui/qt and nativescript
Web UI is not native UI, even if it's technically embedded in a GTK/etc app. Native UI would be using the platform's native controls.
This project looks more similar to Tauri[0] than anything related to native UI.
[0]: https://tauri.app/
But that doesn't make your library native at all — just as Tauri is not native, neither is Sans, and that is the point being made here.
It's not native.
That sounded good, until I saw
> Frontends (Svelte Web Components), Desktops (Qt GTK), Runtimes (NodeJS Deno Bun)
It's basically another React/React-Native, though being based on Svelte could have more compile-time smarts.
I'm particularly unimpressed with NodeJS, and something like Flutter/Dart seems a step up from that.
That said, I'm glad it was made and it was probably a great challenge and joy to have made. Congrats! (I'm just not the target audience.)
deno/bun/node will suffice. I just rewrote it to use nodegui/qt and nativescript
Web UI is not native UI, even if it's technically embedded in a GTK/etc app. Native UI would be using the platform's native controls.
This project looks more similar to Tauri[0] than anything related to native UI.
[0]: https://tauri.app/
But that doesn't make your library native at all — just as Tauri is not native, neither is Sans, and that is the point being made here.
It's not native.