fulcro VS reitit

I definitely believe Clojure needs a rails. Not only will it help beginners get started, if it can help people get started faster and build fast like Django and rails do, I think it'll help more with adoption.

Biff and fulcro seems like they have a shot at this

Biff- https://github.com/jacobobryant/biff

Fulcro - https://github.com/fulcrologic/fulcro

A library that is a bit leaning towards a framework is Fulcro, a fullstack library to build SPAs http://fulcro.fulcrologic.com/

Fulcro (https://github.com/fulcrologic/fulcro) is my web framework of choice whenever I need to create any non-trivial web application thanks to its productivity. Its overarching design goal is sustainable development speed as time goes and code grows and it really shows up. It is developer friendly, with minimal boilerplate, and features you need for any serious application. And it is surprisingly flexible. Fulcro is based on a few simple ideas that combine powerfully to produce a multitude of capabilities, including its Rapid Application Development "add-on". Some people find Fulcro complicated and scary - but it doesn't need to be. Stop choosing "simpler" web frameworks - and ending up implementing half of Fulcro with much more effort and verbosity and much less value. I will present the minimalist way of learning Fulcro with its three corner stones and explain Fulcro's building blocks. After this talk, you will understand the design and value of Fulcro, be motivated to learn it, and equipped to do so quickly.

I am curious how this compares to Fulcro both from a conceptual and a usage perspective. Which advantages does this offer over Fulcro?

Fulcro has a complete "story" for data-driven UIs and backends. https://github.com/fulcrologic/fulcro

We do that via Fulcro: render the first frame in CLJ on JVM, then continue with CLJS in browser. The code is a bit dirty and probably won’t tell you much (because I can’t share the whole app), but you can definitely do that.

I would build the CLJS for your game logic. Then I would build the backend server separately with API endpoints your front end to talk to. https://github.com/metosin/reitit is a pretty good option.

A significant feature of reitit is that routes are composed of simple vectors and maps. That means you can pre-process that data structure however you want before building the router.

You might look at the examples on the Reitit page. Reitit seems to be the emerging library for routing, and it does get you most of the way there, no matter which direction you are looking to go..

for runtime validation & coercion, you can use the pedestal-utilities from reitit which support all of spec, schema and malli. For dev-time var instrumentation (static & dynamic), there are several ways to add those to existing or 3rd party codebases.