clojure
criterium
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.
clojure
- Debugging a memory leak in a Clojure service
-
Clojure 1.12.0 is now available
Here's what I mean by Malli's inability to check macros.
https://github.com/clojure/clojure/blob/ad54fec/src/jvm/cloj...
clojure.spec has a privileged spot in the compiler so that it can validate the data in macros. No other library can do this, because the Clojure compiler directly calls into clojure.spec and does not expose any sort of hook for validating macros.
- Try Clojure
-
Moving your bugs forward in time
For the rest of this post I’ll list off some more tactical examples of things that you can do towards this goal. Savvy readers will note that these are not novel ideas of my own, and in fact a lot of the things on this list are popular core features in modern languages such as Kotlin, Rust, and Clojure. Kotlin, in particular, has done an amazing job of emphasizing these best practices while still being an extremely practical and approachable language.
-
Let's write a simple microservice in Clojure
This article will explain how to write a simple service in Clojure. The sweet spot of making applications in Clojure is that you can expressively use an entire rich Java ecosystem. Less code, less boilerplate: it is possible to achieve more with less. In this example, I use most of the libraries from the Java world; everything else is a thin Clojure wrapper around Java libraries.
-
Top Paying Programming Technologies 2024
5. Clojure - $96,381
-
A new F# compiler feature: graph-based type-checking
I have a tangential question that is related to this cool new feature.
Warning: the question I ask comes from a part of my brain that is currently melted due to heavy thinking.
Context: I write a fair amount of Clojure, and in Lisps the code itself is a tree. Just like this F# parallel graph type-checker. In Lisps, one would use Macros to perform compile-time computation to accomplish something like this, I think.
More context: Idris2 allows for first class type-driven development, where the types are passed around and used to formally specify program behavior, even down to the value of a particular definition.
Given that this F# feature enables parallel analysis, wouldn't it make sense to do all of our development in a Lisp-like Trie structure where the types are simply part of the program itself, like in Idris2?
Also related, is this similar to how HVM works with their "Interaction nets"?
https://github.com/HigherOrderCO/HVM
https://www.idris-lang.org/
https://clojure.org/
I'm afraid I don't even understand what the difference between code, data, and types are anymore... it used to make sense, but these new languages have dissolved those boundaries in my mind, and I am not sure how to build it back up again.
-
Ask HN: Why does the Clojure ecosystem feel like such a wasteland?
As an analogy - my face hasn't changed all that much in a past few years, and I haven't changed my profile picture in those few years. Does it really mean that I'm unmaintained/dead?
> Where can I find latest documentation [...]?
The answer is still https://clojure.org/. And https://clojuredocs.org/ but it's community-maintained so might occasionally be missing some things right after they're released. E.g. as of this moment Clojure 1.11 is still not there since the maintainer of the website has some technical issues deploying the updated version of the website.
For me personally, the best API-level documentation is the source code.
> Where can I find [...] tools / libraries in a easy to use page or section?
There's no central repository of all the available things since they can be loaded from many places (Clojars, Maven Central, other Maven repositories, S3, Git, local files).
But there are community-maintained lists, like the one you've mentioned at https://www.clojure-toolbox.com (fully manual, AFAIK) or the one at https://phronmophobic.github.io/dewey/search.html (automated but only for GitHub). Perhaps there are others but I'm not familiar with them - most of the time, I myself don't find that much value in such services as I'm usually able to find things with a regular web search engine or ask the community when I need something in particular.
-
Why Lisp Syntax Works
They are written in Java, and implement a bunch of interfaces, so the implementation looks complicated, but they are basically just classes with head and tail fields.
https://github.com/clojure/clojure/blob/master/src/jvm/cloju...
- Clojure compiler workshop
criterium
-
Noob has simple program problem.
(criterium does not work here yet b.t.w., but it probably will be working soon)
-
Question about high execution time
criterium, specifically the quick-bench function, will actually run multiple samples an provide a mean runtime (as well as other useful stats) so you can get an idea of what a jit'd warmed up performance looks like. time is great in a pinch, but you end up needing to run it multiple times to ensure optimizations are kicking and and other artifacts (like gc) aren't throwing the results.
-
Logging in Clojure: jar tidiness
I'm going to leave tooling out of this and run everything through a repl on the command line right from the jar. One other thing I want to do is include the incredible criterium library so we can profile. I'm deliberately including criterium separately like this because you shouldn't have a dev-time tool like criterium in an uberjar. And knowing how to easily combine other jars with your real production jar can be very helpful. I grabbed the jar from my .m2 cache.
-
Notes on Optimizing Clojure Code: Overview
I am just going to leave this here - https://github.com/hugoduncan/criterium
-
"The Genuine Sieve of Eratosthenes"
where crit is criterium. As you can see, you're spending most of your time in the seq transformation part.
-
A casual Clojure / Common Lisp code/performance comparison
It's better to benchmark with something like criterium. time is a bit inaccurate. Though, if it's really 15 seconds, I guess will not be that big of a difference
-
Fast and Elegant Clojure: Idiomatic Clojure without sacrificing performance
>>> One of Clojure's biggest weaknesses in practice is that breaking in to those functional structures to figure out where the time is being spent or to debug them is harder than in other languages. This is a natural trade-off of developing a terse and powerful language.
Not that hard if you use something like YourKit. There's also a quite good Clojure library https://github.com/hugoduncan/criterium .
-
Clojure, Faster
Criterium (the benchmarking library used here) uses multiple runs to obtain tighter bounds on amortized performance, as well as techniques to amortize the effects of garbage collection and JIT compilation. See https://github.com/hugoduncan/criterium for a brief overview, as well as links to the pitfalls and statistical techniques involved in JVM benchmarking.
What are some alternatives?
racket - The Racket repository
cl-cuda - Cl-cuda is a library to use NVIDIA CUDA in Common Lisp programs.
malli - High-performance data-driven data specification library for Clojure/Script.
skiko - Kotlin Multiplatform bindings to Skia
trufflesqueak - A Squeak/Smalltalk VM and Polyglot Programming Environment for the GraalVM.
magicl - Matrix Algebra proGrams In Common Lisp.
nbb - Scripting in Clojure on Node.js using SCI
JWM - Cross-platform window management and OS integration library for Java
scala - Scala 2 compiler and standard library. Scala 2 bugs at https://github.com/scala/bug; Scala 3 at https://github.com/scala/scala3
quilc - The optimizing Quil compiler.
scope-capture - Project your Clojure(Script) REPL into the same context as your code when it ran
hash-array-mapped-trie - A hash array mapped trie implementation in c.