miniblog.

Oct 4, 2017 at 22:18

How many bugs are actually code not meeting their spec? IME most bugs are "it would be nice/consistent/robust if it handled $X this way".

Mar 29, 2022 at 06:07

nREPL is supported in several languages, not just Clojure! https://metaredux.com/posts/2019/01/12/nrepl-beyond-clojure.html Interacting with a live instance isn't handled by LSP, so it's interesting to see language-agnostic protocols in this space.

nREPL: Beyond Clojure

Prelude Many people think of nREPL as a Clojure-specific REPL server and that’s perfectly fine. After all the project started its life in the realm of Clojure and the canonical and most widely used implementation is written in Clojure. However, nREPL is much more than its reference implementation and a recent conversation with Phil Hagelberg, reminded me of the significance of this. The default network protocol (socket-based communication with messages encoded using bencode) used is simple, depending neither on JVM or Clojure specifics, thereby allowing (encouraging?) the development of non-Clojure REPL clients. The REPLs operational semantics are such that essentially any non-JVM Clojure implementation should be able to implement it, with allowances for hosts that lack the concurrency primitives to support e.g. asynchronous evaluation, interrupts, etc.

Aug 8, 2020 at 08:08

Clojure is changing how entry points are handled, with a default convention for command line arguments: https://insideclojure.org/2020/07/28/clj-exec/ Re-examining what the main function looks like is a really good exercise!

clj exec – Inside Clojure

Tales of Developing Clojure

Related Posts