uix
reagent
uix | reagent | |
---|---|---|
13 | 41 | |
331 | 4,715 | |
1.5% | 0.1% | |
8.5 | 1.1 | |
2 months ago | 5 months ago | |
Clojure | Clojure | |
Eclipse Public License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
uix
-
Clojure is a product design tool
Check out uix too: https://github.com/pitch-io/uix
…it’s a reagent alternative for modern react.
-
React.dev
> But Reagent supports functional components as well, with hooks and all.
I addressed this already: while reagent is able to emit function components, there is a performance penalty to this.[1]
> I also very much like Hiccup, and so do many of us, because code is data and data is code, and Helix has decided not to support that.
Hiccup is convenient to write, but it is a constant run-time cost and a significant storage cost given that you have to store long series of constructors to cljs.core.PersistentVector in your bundle, have the JS runtime actually construct the vector, then pass it through a Hiccup interpreter to finally produce DOM nodes and throw away the persistent vector, only to repeat this entire process again on re-render.[2]
> Helix has decided not to support that.
That is simply not true. From the Helix documentation[2],
> If you want to use libraries like sablono, hicada or even hx hiccup parser, you can easily add that by creating a custom macro.
These are all Hiccup interpreters you can readily use.
IME there is very little difference between using the $ macro in Helix and writing Hiccup. I do not really miss Hiccup when I use Helix, and you still have data as code ;)
While this is from an unrelated project, there are benchmarks[3] done against Reagent that demonstrate the sheer overhead it has. In practice it is not a big problem if you rarely trigger a re-render, but otherwise it is a non-trivial cost, and if you want to use modern React features (like Suspense), there is a lot of r/as-element mingling going on, converting cases, etc. that simply make Reagent feel more tedious to use than Helix.
Also, the newer UIx2, which largely borrows from Helix, is "3.2x faster than Reagent" according to one of the contributors.[4]
I think it'd be worthwhile to benchmark all of these libraries against each other and record the data in one place. Maybe I'll get around to doing it this weekend :)
---
[1] https://github.com/reagent-project/reagent/blob/master/doc/R...
[2] https://github.com/lilactown/helix/blob/master/docs/faq.md#w...
[3] https://github.com/roman01la/uix#benchmarks
[4] https://github.com/pitch-io/uix/pull/12
-
Thought's on react libraries
If your heart’s set on following React latest closely though, UIx2 seems like a great library, and has a migration path from reagent: https://github.com/pitch-io/uix/blob/master/docs/interop-with-reagent.md
-
UIx v0.8.1
It's been a while since I posted updates on UIx, but here it is, v0.8.1 with API compatibility for React v18.2.0 https://github.com/pitch-io/uix/blob/master/CHANGELOG.md
-
Poignant perspective I found about Clojure's community in r/ExperiencedDevs
I suppose one of the best usecases of code sharing is to do Hydrating Server-Side-Rendered web apps just like Next.js. Not too many other languages are capable of doing this outside of Node and Clojure. For this reason it's kind of surprising that it's not more common in Clojure, seems like most people are just building old fashioned SPA's in Reagent/Reframe rather than competing with Next, but pitch's UIX library does seem to support it https://github.com/pitch-io/uix
-
Structuring Clojure Applications
When I was looking into ClojureScript I was kind of concerned at the complexity of writing applications in ReFrame which seems to be what most of the community seems to be using. I've developed apps in this kind of event-emitting/event handler style before in JavaScript and found it quickly got quite out of hand. For my next app I will want to go with something like React-Query that in a sort of declarative way handles all your data fetching for you, and lets you decouple your components from the getting ahold of the data they depend on. I also searched far and wide for some kind of framework/library that supports SSR+CSR like Next.js but I don't think there's anything ready yet except maybe https://github.com/pitch-io/uix.
-
Is there anything in Clojure comparable to Hotwire in Rails or Phoenix Live View in Elixir? I've had with SPA's.
Might want to check out Uix2 by pitch.io here https://github.com/pitch-io/uix/blob/master/docs/server-side-rendering.md Also there's https://inertiajs.com/ which is pretty interesting and has a 3rd party adapter for clojure https://inertiajs.com/community-adapters
-
reframe or plain reagent for new cljs SPA?
I was starting greenfield I would consider looking further afield, maybe to UIx²
- UIx² : Idiomatic ClojureScript interface to modern React.js from pitch.io
- UIx – Idiomatic ClojureScript interface to modern React.js
reagent
-
Ludic: New framework for Python with seamless Htmx support
Generating `HTML` from lisps has poisoned any other approach for me, see for example https://www.neilvandyke.org/racket/html-writing/, https://reagent-project.github.io/, and https://edicl.github.io/cl-who/
-
Produce HTML from S-Expressions
Hiccup syntax for Clojure uses hash maps (curly braces) for attrs, e.g. `{:style {:background "red" :margin "1em"}`
See Reagent which uses Hiccup synta: https://reagent-project.github.io/
(defn simple-component []
-
A History of Clojure (2020) [pdf]
* Single-Page App: shadow-cljs for the build concerns (https://github.com/thheller/shadow-cljs), Reagent with Re-frame for complex/large app (https://reagent-project.github.io and https://github.com/day8/re-frame). Even if we now prefer using HTMX (https://htmx.org) and server-side rendering (Hiccup way of manipulating HTML is just amazing, https://github.com/weavejester/hiccup).
- Leaving Clojure - Feedback for those that care
-
Clojure is a product design tool
The API documentation lists the most commonly and rarely used parts before going into detail and there are many usage examples.
Reagent has a nice intro tutorial (classic todo-app): http://reagent-project.github.io and many other helpful tutorials and resources for beginners: https://cljdoc.org/d/reagent/reagent/1.2.0/doc/documentation...
However, since Reagent is still stuck with class-components for more complex behavior and relies on Hiccup, which is nice but has a performance cost compared to pure React, I am unsure about its future. Like some others in the Clojure community, I have moved to thin React wrappers like Helix and use Refx to integrate those with re-frame. It may be a bit confusing right now for beginners since there is no “golden path”.
Also, unfortunately, many smaller libraries are poorly documented and it seems like it is expected from the developer to dig into the source code to find out what’s going on.
What I found the most difficult as a beginner was how to setup a project in ClojureScript in the first place, like all the configuration in shadow-cljs, how it interacts with deps.edn, how it integrates with npm, the REPL, etc. But dev/build config has always been a weak spot for me, so it might be just that.
Overall, I still very much enjoy working with Clojure(Script), more than in any other language. Anyone who likes Lisps and functional programming should give it a try (and be sure to watch Rich Hickeys amazing talks!).
-
Ask HN: How can a BE/infra developer handle the FE side of personal projects?
have you tried cljs and reagent? it’s a different vibe.
my bootstrap: https://github.com/nathants/aws-gocljs
the project: https://reagent-project.github.io/
- What are the enduring innovations of Lisp? (2022)
-
Building a website like it's 1999... in 2022
Clojure people have been doing this for a decade or so. It’s really so much better to work with. All started with Hiccup and when React came along you got Reagent and many more developments building on the idea.
-
React.dev
> But Reagent supports functional components as well, with hooks and all.
I addressed this already: while reagent is able to emit function components, there is a performance penalty to this.[1]
> I also very much like Hiccup, and so do many of us, because code is data and data is code, and Helix has decided not to support that.
Hiccup is convenient to write, but it is a constant run-time cost and a significant storage cost given that you have to store long series of constructors to cljs.core.PersistentVector in your bundle, have the JS runtime actually construct the vector, then pass it through a Hiccup interpreter to finally produce DOM nodes and throw away the persistent vector, only to repeat this entire process again on re-render.[2]
> Helix has decided not to support that.
That is simply not true. From the Helix documentation[2],
> If you want to use libraries like sablono, hicada or even hx hiccup parser, you can easily add that by creating a custom macro.
These are all Hiccup interpreters you can readily use.
IME there is very little difference between using the $ macro in Helix and writing Hiccup. I do not really miss Hiccup when I use Helix, and you still have data as code ;)
While this is from an unrelated project, there are benchmarks[3] done against Reagent that demonstrate the sheer overhead it has. In practice it is not a big problem if you rarely trigger a re-render, but otherwise it is a non-trivial cost, and if you want to use modern React features (like Suspense), there is a lot of r/as-element mingling going on, converting cases, etc. that simply make Reagent feel more tedious to use than Helix.
Also, the newer UIx2, which largely borrows from Helix, is "3.2x faster than Reagent" according to one of the contributors.[4]
I think it'd be worthwhile to benchmark all of these libraries against each other and record the data in one place. Maybe I'll get around to doing it this weekend :)
---
[1] https://github.com/reagent-project/reagent/blob/master/doc/R...
[2] https://github.com/lilactown/helix/blob/master/docs/faq.md#w...
[3] https://github.com/roman01la/uix#benchmarks
[4] https://github.com/pitch-io/uix/pull/12
-
React is a fractal of bad design
Reagent is peak React. All the good stuff without any of the hook and readability problems the article describes.
No affiliation, happy user for years.
https://github.com/reagent-project/reagent
What are some alternatives?
reagent-utils - a collection of helper functions for use with Reagent
helix - A simple, easy to use library for React development in ClojureScript.
re-frame - A ClojureScript framework for building user interfaces, leveraging React
clj-stimulus - Clojure wrapper for Stimulus
shadow-cljs - ClojureScript compilation made easy
babashka-htmx-todoapp - Quick example of a todo list SPA using Babashka and htmx
fulcro-rad-demo - A demo for Fulcro RAD using either SQL or Datomic databases.
clojure-inertia-pingcrm-demo - PingCRM on Clojure - A Clojure/Script fullstack demo application to illustrate how Inertia.js works.
storybook.js-with-shadow-cljs
kee-frame-sample - Demo application to show off features of kee-frame
hyperscript - Create HyperText with JavaScript.