off-topic 2021-03-12 | Slack Archive

Just droppin’ this here:

;; my main work REPL:
dev=> (up-since)
#inst "2021-02-26T00:06:35.865-00:00"
;; my depstar project REPL:
dev=> (up-since)
#inst "2021-03-04T23:02:58.207-00:00"
;; my HoneySQL v2 project REPL:
user=> (dev/up-since)
#inst "2021-01-31T00:34:55.324-00:00"

(my dot-clojure project has a :dev/repl alias that starts a variety of REPLs and makes the up-since function available)

🙂 3

👍 7

seancorfield02:03:44

When I’m talking about my RDD workflow and never using refresh/reload tooling… ☝️:skin-tone-2:

vemv03:03:54

I'd see it more of an evidence that startup time doesn't matter (which also is a useful point!) one can have long-running sessions with or without tools.namespace, can be considered orthogonal? my t.n sessions never become unusable (`(clear)` is a thing if things get messy)

seancorfield04:03:09

💯 for the startup time issue, yeah. I don't know how long-lived REPLs are for folks that do use that refresh/reload workflow -- I don't hear them talk about that. Which is partly why I make a point of showing just how long I keep my REPLs open.

blak3mill3r05:03:17

I use the refresh/reload style... my repls stay open until I need a new dependency that I cannot add with add-libs ... or if I do something stupid and lock the process up for example. I don't measure repl-uptime, and my newer (non-lein) projects start pretty quickly so this does not matter as much as it once did. I know my repls sometimes get used for many days, though.

seancorfield05:03:22

Ah, nice to see someone else using add-libs!

blak3mill3r09:03:39

Got addicted when I was using leiningen

Mno08:03:11

I crash things in ways that can only be fixed by restarting the repl more often than that 😅

borkdude10:03:27

Reminder: we have a #releases channel for releases that are just about bug fixes and/or minor enhancements, that do not belong in #announcements. Feel free to join there!

👍 9

2021-03-12

Channels