kobweb VS Svelte

Done, added "Other" and "None of the above" options. Thanks for the feedback! Btw, were you talking about this library: https://github.com/varabyte/kobweb?

Aaaaand sourcemap config done: https://github.com/varabyte/kobweb/commit/84e17b710d92332efdb37abb887e546a7f03c73d

(For people who don't know Kobweb, you can read more at https://github.com/varabyte/kobweb, but until I update it, please replace "Compose for Web" to "Compose HTML" in your head, thanks!)

I'm actively working on https://github.com/varabyte/kobweb, which builds on top of Compose for Web and adds some extra support to make it a little easier for Android developers to get into. (You will ultimately need to learn html / css but I believe Kobweb makes that a little easier to start getting used to it).

https://github.com/varabyte/kobweb is Compose for Web using DOM rendering instead of Canvas with a Jamstack like approach. Worth to try and if it later upgrade from Kotlin/JS to Kotlin/Wasm, it could really become something big …

I'm working on https://github.com/varabyte/kobweb which is not mature, but you might want to check it out anyway?

This is indeed a very important point, and I care deeply about that.

For Compose for Web, there has been I think a lot of debate to decide if the Web rendering should be Canvas or DOM based. At least for now, it seems the official support is focusing on Canvas rendering for pixel-perfect rendering, and it already works with Koltin/Wasm, see https://news.ycombinator.com/item?id=34779746. This choice is probably driven by Kotlin current mobile app main use case.

But via community-driven project like https://github.com/varabyte/kobweb or https://github.com/mpetuska/kmdc, Compose for Web can also be a good Web citizen and perform DOM based rendering.

I'm working on an opinionated framework on top of their framework called Kobweb, but depending on your goals it may be sightly too early to use it.

This may not help but I have a working ktor server in my project. Here's my Gradle config: https://github.com/varabyte/kobweb/blob/main/backend/server/build.gradle.kts

React has introduced measures like batching state updates, background concurrent rendering and memoization to tackle this. My opinion is that the best way to solve the problem is by improving their reactivity model. The app needs to be able to track the code that should be re-run on updating a given state variable and specifically update the UI corresponding to this update. Tools like solid.js and svelte work in this manner. It also eliminates the need for a virtual DOM and diffing.

Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…

Svelte is a powerful web framework that offers a fresh approach to building web applications. Its simplicity, reactivity model, and built-in features make it an excellent choice for developers looking to create efficient and maintainable applications. By following this guide, you should now have a good understanding of how to get started with Svelte and build your first components, routes, and transitions. You can read more about svelte on the official Svelte website.

Use .NET features (especially dotnet watch) as a setup for a client-side Svelte application, starting from a simple C# console app.

Volar originally was Vue3's language support tool for VScode (I don't know about other editors). By today, volar has become a language indipendent framework to create language tools. It might still be a bit early for the dev with skill issues like me to use it and build some tools, but astro and svelte already use Volar to create their language tools.