re-frame
ring
re-frame | ring | |
---|---|---|
23 | 15 | |
5,376 | 3,708 | |
-0.1% | 0.3% | |
9.1 | 8.4 | |
about 1 month ago | about 1 month ago | |
Clojure | Clojure | |
MIT 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.
re-frame
-
Goodbye, Clean Code
This article always reminds me of this excerpt from re-frame’s docs [0]:
> Now, you think and design abstractly for a living, and that repetition will feel uncomfortable. It will call to you like a Siren: "refaaaaactoooor meeeee". "Maaaake it DRYYYY". So here's my tip: tie yourself to the mast and sail on. That repetition is good. It is serving a purpose. Just sail on.
[0]: https://github.com/day8/re-frame/blob/master/docs/correcting...
-
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).
-
Is there an open source project focused on ClojureScript, React, Reagent?
Big and/or complete projects that use re-frame The main list: https://github.com/day8/re-frame/blob/master/docs/External-Resources.md
-
Reflet introduces descriptions: a new kind of polymorphic query
Reflet is a set of tools for building Re-frame + React based web apps with graph and non-graph data models. This includes:
-
Were React Hooks a Mistake?
https://github.com/day8/re-frame
Notably the author of re-frame has been weary of hooks.
I think that’s for a good reason. The approach in re frame feels like the best way to manage state so far for a react based app. Everything that changes state flows through an event. State can only be observed through subscriptions. Side effects are isolated to their own type of event. Debugging and testing are so straight forward with these concepts.
Redux got close but it has two problems in my mind. Like hooks, it encapsulates for no good reason. Put the state in one thing that you can observe holistically before and after pure events. It also has too much boiler plate.
-
Clojure Turns 15 panel discussion video
The cljs stack I hear about a lot (and use) is ShadowCLJS with reagent (https://reagent-project.github.io/) and re-frame (https://day8.github.io/re-frame/). ShadowCLJS is more of a build tool, but is really well documented and easy to use. Reagent is basically react but a simpler API, and re-frame is a layer on top of that provides data subscriptions and event-handlers to manage app state. It's overkill for some apps but I find it's actually super easy to work with and not as much complexity as I thought.
For backend there is luminus (https://luminusweb.com/) or Kit (https://kit-clj.github.io/). They are basically project templates that wire together a ton of popular solutions for various things - database access, migrations, security, html templating, etc. Also includes frontend frameworks like re-frame if you want.
-
Reflet: building Re-frame + React based web apps with graph and non-graph data models
Reflet aims to be a natural progression on top of Re-frame to support complex, data driven requirements. In that sense, it is both easy to learn, but powerful. You could say it's sort of like Re-frame++ (or Fulcro for Re-frame). Its main design goals are:
-
Killing mutants to improve your tests
At my current client we're working on having a frontend architecture for writing SPAs in JavaScript similar to re-frame's one: an event-driven bus with effects and coeffects for state management[1] (commands) and subscriptions using reselect's selectors (queries).
-
Giving new life to existing Om legacy SPAs with re-om
Some of us had worked with effects and coeffects before while developing SPAs with re-frame and had experienced how good it is. After working with re-frame, when you come to horizon, you realize how a good architecture can make a dramatic difference in clarity, testability, understandability and easiness of change.
-
what componies uses Clojure, and what componies deceased the use of other languages after additions of Clojure, for example Dropbox decrease the use of python after addition of Go programming language, are there any similar story with Clojure?
https://youtu.be/geeK1-jjlhY (talk about an initial prototype with re-frame and the decision to do a rewrite in Clojure)
ring
-
A History of Clojure (2020) [pdf]
* HTTP: Ring is the de facto way to manage HTTP request (see https://github.com/ring-clojure/ring/wiki/Concepts). Jetty and Aleph are common web servers (and https://github.com/clj-commons/aleph) that implement Ring interface.
- Como desenvolvi um backend web em Clojure
-
what componies uses Clojure, and what componies deceased the use of other languages after additions of Clojure, for example Dropbox decrease the use of python after addition of Go programming language, are there any similar story with Clojure?
https://youtu.be/LcpbBth7FaQ (really cool live coding session with REPL-driven development for a ring web app)
-
I Don’t Like Go’s Default HTTP Handlers
> In the HTTP handlers it makes sense that you don't have return values, because: What would you do with that value exactly?
I think that approach used by clojure's ring shows an elegant way to represent http responses https://github.com/ring-clojure/ring/wiki/Concepts#responses. They are essentially structs with the following fields:
status := number
headers := map of string->string
body := stream | string | seq | inputstream
Request handlers are handed a request struct that is similar. The handler is a function that maps a request to a response (it doesn't actually write to streams itself).
I like this style for an http library for a couple of reasons:
1. HTTP resources can be viewed as functions whose domain is the request, and range is the response. Having the abstraction match that makes for really nice code.
-
what web framework do you use?
While you won't find your Spring here, you will find that many of those web libraries will tend to use or produce Hiccup, return Ring maps or maybe have pipelines built using interceptors. Composing libraries together is usually not that hard, but it does require you to leave the comfort zone of the framework's abstractions to try to understand what is actually happening e.g. when someone makes an HTTP request and something is returned and displayed in the browser.
-
Microhttp is an event-driven, single-threaded, zero-dependency web server with 500 LOC. Benchmarks on EC2 show 100,000+ requests per second and 50,000+ persistent connections.
On that note, are you able to support everything required by the ring spec?
-
is bulding rest apis with clojure a good idea ?
You can check out my example project in Clojure with using Ring.
- Clojure Ring เบื้องต้น
-
Diving into clojure
It uses already mentioned ring api (https://github.com/ring-clojure/ring/wiki).
-
Can someone help me understand ring's async handlers (specifically, with Jetty)
I've tried to pair down to the simplest example which shows the issue, and raised it here as I couldn't see one you'd already created or similar: https://github.com/ring-clojure/ring/issues/436 This is so that I have something to link to/follow from our side, hope you don't mind, and many thanks for the diagnosis!
What are some alternatives?
reagent - A minimalistic ClojureScript interface to React.js
Jetty - Eclipse Jetty® - Web Container & Clients - supports HTTP/2, HTTP/1.1, HTTP/1.0, websocket, servlets, and more
fulcro-rad-demo - A demo for Fulcro RAD using either SQL or Datomic databases.
usermanager-reitit-integrant-example - A little demo web app in Clojure, using Integrant, Ring, Reitit, Selmer (and a database)
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.
ring-netty-adapter - Netty Support for Ring
Elm - Compiler for Elm, a functional language for reliable webapps.
ketu - A clojure kafka client with core.async integration.
reitit - A fast data-driven routing library for Clojure/Script
clojure-polylith-realworld-example-app - Clojure, Polylith and Ring codebase containing real world examples (CRUD, auth, advanced patterns, etc) that adheres to the RealWorld spec and API.
django-extensions - This is a repository for collecting global custom management extensions for the Django Framework.
clojure - The Clojure programming language