ReactFX
jotai
ReactFX | jotai | |
---|---|---|
3 | 107 | |
370 | 17,342 | |
- | 1.7% | |
10.0 | 9.3 | |
over 5 years ago | 1 day ago | |
Java | TypeScript | |
BSD 2-clause "Simplified" License | 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.
ReactFX
-
React is a fractal of bad design
You could also write that in many other languages like Clojure (with cljfx for FP fans), Python, Ruby, JavaScript, and of course Java. It would be less verbose if I used a library that better used Kotlin's features, but the goal here is that you can look up the JavaFX APIs from the link above (there are a couple of implied static imports).
So not much different, but it demonstrates how the text property of the label is bound to a dynamically computed string which is in turn bound to an observable number. When the timer fires, the count increases and the label is recomputed. Everything is done that way so layout computations, for example, won't run unless the size of the label changes. And that's it - no need for VDOMs or prop drilling or state memoization or any of these other performance hacks.
At some point you'll observe that this seems a like like "reactive programming" as used on the server side, and then might want to explore a library like ReactFX which connects these two worlds together.
https://github.com/TomasMikula/ReactFX
There are some other nice features in this type of toolkit that the web community seems to be heading towards. I'd be willing to bet a lot that at some point they'll even reinvent inheritance under a new name, because being able to write code that's generic over component trees is really pretty useful. The hooks/functions model totally wrecks that and has led to this explosion of "design systems" (otherwise known as themes), none of which interoperate properly or can be coded against in an abstracted manner.
None of this is to say that FX is perfect or that React/SolidJS etc are the wrong tools to use. You can run FX apps in a browser using a form of server side rendering - check out https://www.jpro.one to see a fully crawlable website that's actually implemented using JavaFX on the server with no frontend/backend split existing at all. But it only works well if you don't have a fast and reliable server connection, plus a server with plenty of RAM and CPU. Alas browsers pull all sorts of mean tricks to keep people locked inside the HTML5 sandbox so JS frameworks aren't going anywhere, but it would be nice if that community spread its wings a bit and looked at prior art from outside their language. GUIs are old and the challenges involved in them aren't new, and from the outside it looks suspiciously like there is no real progress being made here, only wheel spinning.
-
RichTextFX: Open source libraries for making a text viewer / editor
ReactFX - For cleaner, easier-to-reason event handler composition. Nice!
-
What is this design pattern called is prevalent throughout guava and apache commons?
I've noticed when you look into a lot of classes in some libraries like guava, apache commons, or ReactFX, you'll notice a sort of abstraction pattern. There'll be a class that houses a bunch of common methods. Inside of those methods, instead of putting the relevant logic inside of the method, they'll call an operation-specific class that executes the logic. An example would be PredicateUtils or EventStream. Is there name for this pattern? It doesn't quite seem like it fits the command or service layer patterns.
jotai
-
React Server Components Example with Next.js
Daishi Kato, creator of Zustand and Jotai, says there are a few things we need to support RSC serialization:
- 5 Alternatives to Redux for React State Management
-
jotai-wrapper, a super tiny and simple utility library
I've just published jotai-wrapper, a super tiny and simple utility library that makes using jotai even simpler. It comes from the necessity to migrate a project with react-context-slices to jotai. Both libraries share a similar API. While in react-context-slices you have the useSlice hook, in jotai you have the useAtom, useSetAtom, and useAtomValue hooks. In react-context-slices you define either React Context or Redux slices, while in jotai you define atoms. The need for the migration from the first to the second was a high memory usage by react-context-slices when using React Context slices.
-
React State Management in 2024
Atom-based: splits states into tiny pieces of data called atoms, which can be written to and read from using React hooks. In this group, we have Recoil and Jotai.
-
React Basics: Essential Knowledge for Every React Developer
jotai Is the signal based state manager I recommended, offering the best developer experience (in my opinion) as it eliminates the necessity to define and update a global store
-
🚀 Dominate React Project Startups: Insider Tips for Dev Success! 🤓
Jotai 🧙♂️
- Jotai – Primitive and flexible state management for React
-
Thoughts on Signals?
Atomic libs include Recoil, Jotai, and the one I maintain: Zedux. Zedux especially was designed to work well with sockets and RxJS observables and has been getting some traction recently, so of course I recommend checking it out. Feel free to hmu with any questions.
-
New Project: What is a good framework for a website?
Global State Machine: Jotai (great for any state that needs to be stored globally for your application)
- Is there a state management library, similar to Redux or Zustand, that automatically generates setters for the state you define?
What are some alternatives?
RichTextFX - Rich-text area for JavaFX
zustand - 🐻 Bear necessities for state management in React
Flowless - Efficient VirtualFlow for JavaFX
redux-toolkit - The official, opinionated, batteries-included toolset for efficient Redux development
commons-collections - Apache Commons Collections
Recoil - Recoil is an experimental state management library for React apps. It provides several capabilities that are difficult to achieve with React alone, while being compatible with the newest features of React.
signals - Manage state with style in every framework
react-query - 🤖 Powerful asynchronous state management, server-state utilities and data fetching for TS/JS, React, Solid, Svelte and Vue. [Moved to: https://github.com/TanStack/query]
react-hook-form - 📋 React Hooks for form state management and validation (Web + React Native)
valtio - 💊 Valtio makes proxy-state simple for React and Vanilla
redux-thunk - Thunk middleware for Redux
hookstate - The simple but very powerful and incredibly fast state management for React that is based on hooks