realworld VS kobweb

In light of all this, it became exceedingly clear that someone else needed to step in and help. Why not me? Well, it can be me. And, after 3 months of development, I am happy to announce (again) dwayne/elm-conduit (demo), an open-source Elm SPA for RealWorld's Medium.com clone.

https://github.com/gothinkster/realworld

It's just for web app (a Todo app). Your GIS AND CLI ideas are interesting, I haven't seen anything similar to realworld for those.

View on GitHub

So what would be a better benchmark? Perhaps a "standard" "real world" app, like https://github.com/gothinkster/realworld

Or something simpler?

RealWorld example app is a full-stack application called "Conduit" that consists of a backend that serves JSON API and a frontend UI. There are numerous implementations for different languages and frameworks, but in this tutorial you will be using the Spring backend and the React frontend.

Github has millions of projects, some large fraction with more than 100 stars, so it doesn't seem like you are searching very hard. But more importantly, why "100 stars"? Stars are meaningless and arbitrary. Many developers use stars like bookmarks. I just did a quick search and noticed a project like realworld (just a demo for learning, 65 contributors) has have more stars than Bitcoin (900+ developers, perhaps you have heard of it?)

I feel you, context API sometimes overcomplicates everything. Let me introduce to you RealWorld. It is a great project that uses composition to make its structure scalable. It is actually a codebase that implements various fragments of a larger scale project such as Medium or Twitter. Check it out here: https://github.com/gothinkster/realworld. I hope this helps!

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