These resources (articles, books, and videos) are useful when you're starting to learn the language, or when you're learning a specific part of the language. This an opinionated list, no doubt. I've compiled this list from writing and teaching Clojure over the last 10 years.
| ; run `bb backup` to backup database | |
| ; run `bb restore` to restore latest backup | |
| {:min-bb-version "0.4.0", | |
| :tasks {; CONSTANTS | |
| db-name "dev_blog", | |
| backup-dir "backups", | |
| now (str (java.time.LocalDateTime/now)), | |
| ; TASKS | |
| create-backup-dir {:depends [backup-dir], :task (babashka.fs/create-dirs backup-dir)}, |
If you're encountering ping github.com failing inside WSL with a Temporary failure in name resolution, you're not alone — this has been a long-standing issue, especially when using VPNs or corporate networks.
This issue is now fixed robustly with DNS tunneling, which preserves dynamic DNS behavior and avoids limitations like WSL’s former hard cap of 3 DNS servers in /etc/resolv.conf.
DNS tunneling is enabled by default in WSL version 2.2.1 and later, meaning that if you're still seeing DNS resolution issues, the first and most effective fix is simply to upgrade WSL. Upgrading WSL updates the WSL platform itself, but does not affect your installed Linux distributions, apps, or files.
To upgrade WSL, follow these steps,
How do you send information between clients and servers? What format should that information be in? What happens when the server changes the format, but the client has not been updated yet? What happens when the server changes the format, but the database cannot be updated?
These are difficult questions. It is not just about picking a format, but rather picking a format that can evolve as your application evolves.
By now there are many approaches to communicating between client and server. These approaches tend to be known within specific companies and language communities, but the techniques do not cross borders. I will outline JSON, ProtoBuf, and GraphQL here so we can learn from them all.
| ;; I think it would be a mistake to introduce temporal coupling to prevent typos. | |
| ;; The example program below lets you identify "missing" keys specs at | |
| ;; the time and place of your choosing, and then handle them as you | |
| ;; deem appropriate, without imposing those decisions on other | |
| ;; users of spec. | |
| (require '[clojure.spec.alpha :as s] | |
| '[clojure.set :as set]) |
If you hate git submodule, then you may want to give git subtree a try.
When you want to use a subtree, you add the subtree to an existing repository where the subtree is a reference to another repository url and branch/tag. This add command adds all the code and files into the main repository locally; it's not just a reference to a remote repo.
When you stage and commit files for the main repo, it will add all of the remote files in the same operation. The subtree checkout will pull all the files in one pass, so there is no need to try and connect to another repo to get the portion of subtree files, because they were already included in the main repo.
Let's say you already have a git repository with at least one commit. You can add another repository into this respository like this:
| ;; spec errors are data, and as such are composable with all the rest | |
| ;; of Clojure. The forms below show getting to an interesting part | |
| ;; of an error in a larger data structure, taking advantage of | |
| ;; edn-reading, pretty-printing, *print-length* and threading macro. | |
| ;; It is difficult to maintain the compositionality shown here | |
| ;; once you convert error data into e.g. ASCII art. | |
| (require | |
| '[clojure.edn :as edn] |
| export default class GeoJsonMapLayer extends React.Component { | |
| render() { | |
| return ( | |
| <div> | |
| </div> | |
| ); | |
| } | |
| componentWillUnmount() { | |
| if (this.layer) { |
| (ns user.defn+spec | |
| (:require [clojure.spec :as s])) | |
| (defn non-&-sym? [x] (and (symbol? x) (not= '& x))) | |
| (s/def ::arglist | |
| (s/cat :normal-args (s/* (s/cat :name non-&-sym? | |
| :spec-form (s/? (s/cat :- #{:-} | |
| :spec ::s/any)))) | |
| :varargs (s/? (s/cat :& #{'&} |
| (defrecord Retry [bindings]) | |
| (defmacro with-retry | |
| "It's really fucking inconvenient not being able to recur from within (catch) | |
| expressions. This macro wraps its body in a (loop [bindings] (try ...)). | |
| Provides a (retry & new bindings) form which is usable within (catch) blocks: | |
| when this form is returned by the body, the body will be retried with the new | |
| bindings." | |
| [initial-bindings & body] | |
| (assert (vector? initial-bindings)) |