refx
uix
refx | uix | |
---|---|---|
3 | 1 | |
126 | 428 | |
- | - | |
1.9 | 0.0 | |
about 1 year ago | 7 months ago | |
Clojure | HTML | |
MIT License | Eclipse Public License 2.0 |
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.
refx
-
React.dev - are CLJS developers using Reagent in trouble?
[1] https://github.com/lilactown/helix [2] https://github.com/ferdinand-beyer/refx
- React.dev
- refx 0.0.49 release -- re-frame implementation without reagent
uix
-
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
What are some alternatives?
helix - A simple, easy to use library for React development in ClojureScript.
uix - Idiomatic ClojureScript interface to modern React.js
racing-game-cljs - A 3D racing game built with ClojureScript, React and ThreeJS
template - A simple framework for webapps
instantsearch - ⚡️ Libraries for building performant and instant search experiences with Algolia. Compatible with JavaScript, TypeScript, React and Vue.
reagent - A minimalistic ClojureScript interface to React.js
klipse - Klipse is a JavaScript plugin for embedding interactive code snippets in tech blogs.
zaiste.net - Zaiste is a software technologist who helps companies and brands build great software products. Expertise in: Java, Ruby, Python, JavaScript and Clojure.