core.async
ring
core.async | ring | |
---|---|---|
9 | 15 | |
1,934 | 3,710 | |
-0.2% | 0.4% | |
5.1 | 8.2 | |
3 months ago | 8 days ago | |
Clojure | Clojure | |
Eclipse Public License 1.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.
core.async
-
How to handle concurrency in Clojure with core.async
Hey, how you doing? This article was written right after I had to painstakingly read the clojure.core.async source code in order to finish a task. So, I hope I save you from the same fate as I had 😄.
- Como desenvolvi um backend web em Clojure
-
Comparison of manifold and clojure.core.async
It was created by Rich Hickey: https://github.com/clojure/core.async/commit/47b1d24c0291050a1188dbeee2fc9227f694eb3c don't think he's disavowed it lol.
-
Sleeping is not the best option
Some time ago we developed some helpers using the capturing notifications strategy to test asynchronous ClojureScript code that was using core.async channels. Have a look at, for instance, the expect-async-message assertion helper in which we use core.async/alts! and core.async/timeout to implement this behaviour. The core.async/alts! function selects the first channel that responds. If that channel is the one the test code was observing we assert that the received message is what we expected. If the channel that responds first is the one generated by core.async/timeout we fail the test. We mentioned these async-test-tools in previous post: Testing Om components with cljs-react-test.
-
What is the difference between Manifold and core.async?
Hi there I'm using Clojure almost a year. I've played with both Manifold and core.async a bit but I'm not %100 sure when to use core.async over Manifold or vice versa.
-
Rich Hickey – open-source is Not About You
If you're not familiar with lisps in general, it might be hard to grok the differences between lisp-macros (as used in Clojure) and "normal" macros you see in other languages.
But, if you are familiar already, and just wanna see examples of neat macros that makes the API nicer than what a function could provide, here are a few:
- https://github.com/clojure/core.async/blob/master/examples/w...
- https://github.com/weavejester/compojure
- https://github.com/ptaoussanis/timbre
- https://github.com/krisajenkins/yesql
-
The Clojure Mindshare (2019)
https://github.com/clojure/core.async
> and with a very poor tooling (lack of IDE's)
Lisps have fantastic support in Emacs and VSCode and are in general simple enough languages that often the heavyweight of an IDE is not needed. But if you want IDEs there are:
- 6 Years of Professional Clojure
-
Equivalent of select in core.async?
If you don't want to block the current thread, you can do the looking/waiting on another thread via thread or in a go using alts! .
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?
promesa - A promise library & concurrency toolkit for Clojure and ClojureScript.
Jetty - Eclipse Jetty® - Web Container & Clients - supports HTTP/2, HTTP/1.1, HTTP/1.0, websocket, servlets, and more
cloroutine - Coroutine support for clojure
usermanager-reitit-integrant-example - A little demo web app in Clojure, using Integrant, Ring, Reitit, Selmer (and a database)
zio-schema - Compositional, type-safe schema definitions, which enable auto-derivation of codecs and migrations.
ring-netty-adapter - Netty Support for Ring
lein-ancient - Check your Projects for outdated Dependencies
ketu - A clojure kafka client with core.async integration.
yesql - A Clojure library for using SQL.
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.
shadow-cljs - ClojureScript compilation made easy
clojure - The Clojure programming language