specter VS fulcro

> Another example is Specter. Specter is a generically useful library for querying and manipulating data structures

> https://github.com/redplanetlabs/specter/tree/master/src

> MutableCell.Java. 8 years ago

  package com.rpl.specter;

If you are truly interested in understanding my point of view -- a great way to do it would be to learn how to use this Clojure DSL: https://github.com/redplanetlabs/specter

For deeply nested data, use specter https://github.com/redplanetlabs/specter

Yes :), I needed a fast dijkstra implementation to solve a puzzle in 2021. A pure clojure implementation was too slow so i built one on top of this https://github.com/redplanetlabs/specter

https://github.com/redplanetlabs/specter (very powerful way to express modifications to nested data)

Don't forget about specter which is efficient and compact due to its DSL.

Learn and use specter for nested data manipulation, will take some studying but is a more general solution (https://github.com/redplanetlabs/specter)

For part 1, the version (and other things) are attached to the metadata of each sexp, and a Specter recursive path is used to extract all of the versions.

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.