HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
candid82
joker
Go2017–2024
candid82 / joker

joker

Small Clojure interpreter, linter and formatter.

19Distinct people
22Mentions
0Explicit recommenders
1.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Small Clojure interpreter, linter and formatter.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 7:27:27 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year22 dated mentions

Observed mentions: 2017-02-17 21:13:20 UTC to 2024-08-30 23:09:40 UTC.

0123452017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC202
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC211
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC505
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC505
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC202
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC413
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC202

What Hacker News says

5 sources
Ya, GraalVM fixes it. But it requires a compile step, so it's not as nice for scripts. My favourite for scripting right now is Joker: https://github.com/candid82/joker Joker is a Clojure dialect which is interpreted, thus it starts super fast (but runs slower, but fast enough for scripts). Its design is to be batteries included for all things scripting. So it's just a self contained executable with everything you need for scripting. It's implemented in Go. I use it wherever I would have used bash or powershell prior. There is also Babashka: https://github.com/borkdude/babashka which is a similar idea, it's an interpreted dialect of Clojure with fast start times designed for scripting. The difference with Joker is that it is newer and more experimental, and it is implemented in JVM Clojure, compiled with GraalVM and has no Windows support
Read the rest
for now. Anyways, I really recommend the use of Joker. Its awesome for scripting. I just put its binary in all my bin folders and script with it. It's great.
In Larry Wall has approved renaming Perl 6 to Raku
I found managing production JVM is amazing. In fact, little other runtimes come close in my opinion. What don't you like about it? For scripting, there's a lot of ways to script efficiently with Clojure, it's actually great for it as well. So, for most my scripts, I don't really mind waiting 1 second for them to start. That said, if you wanted them to start faster, using ClojureScript takes you under 100ms. And using Joker (https://github.com/candid82/joker) takes you under 50ms. When I need even faster startup for scripts and also need performant runtime, I've been using GraalVM to compile to native binaries, those start in under 10ms, and execute much faster than ClojureScript and Joker. That's a good strategy if you want to write things like a grep tool, or ls, or a linter, code formater, etc.
In Why Clojure?
WalmartLabs | Software Engineering (Clojure) | SF or REMOTE | FULL TIME We're a small close-knit team backed by big company resources. We write mission-critical, robust software that's used by millions of Walmart's customers daily. Our suite of software includes but is certainly not limited to: - a large distributed system that processes all store transactions from every Walmart and Sam's Club store in the US. If you've ever used Walmart Pay, this is how you get your receipt! - a massive GraphQL service that powers all customer purchase & returns history for all platforms (written using our own open-source GraphQL implementation for Clojure: https://github.com/walmartlabs/lacinia). We roll out new marquee customer-facing features in this service almost weekly: everything from tire installation services to bakery orders to propane tanks. -
Read the rest
services to allow customers to manage and purchase care plans - push notifications Our tech stack is: Clojure (for everything!), GraphQL, Cassandra, Kafka, Redis, Prometheus, Ruby (for some infrastructure tasks) Here's a few things we value that you should have: - A self-starter, curious, and DIY attitude. A lot of our bedrock technology is home-grown and written to solve our own unique Walmart-scale problems. One of the engineers on our team wrote an entire Clojure dialect (https://github.com/candid82/joker/), and scripts written in that language now do a lot of heavy lifting of our own infrastructure. - A good intuition for writing code that won't fall over under pressure and handles failure states well. We deploy daily and a null pointer might impact millions of requests in a few minutes. - An interest in doing DevOps-y stuff and a high expectation in good monitoring. We have full ownership of the life-cycle of our code and the servers it runs on. - The ability to think and work in functional languages (Clojure) - Experience writing distributed systems with a lot of message passing If this sounds interesting to you, please reach out to bcarrell@walmart.com and say hello.
In Ask HN: Who is hiring? (April 2019)

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.