it's components all the way down 🌀 nothing much to add myself, I've used Component to model modules in a modular app (Polylith style), or "repositories" as in data stores, etc. I guess there's no universal answer as there are many ways of an architecting an app.

I maintain a fairly large (~50kloc) web app/SPA in Clojure/Script. Initially I used Component but just for stateful things: web server, DB connection pool, and a handful of thread pools, but I recently decided that Component really wasn’t helpful for such a small number of components. Now I just have functions to start/stop the app by starting those components and passing the dependencies explicitly. For example, the thread pools usually need the DB connection pool, so I start the DB pool first, then pass it to each thread pool as I start it.

I created some Ring middleware to inject all the components into the request map so that web endpoint handlers can pull in whatever they need (typically just the DB pool).

$ signifies the prompt, mostly to distinguish user input from a program output.

Compare e.g.

$ echo yes
yes

echo yes
yes

Also, $ often means "unprivileged user" and # means root.

hadn't realized that convention. neat. thanks

Ooh, now that is a good reason there. I can get behind that

At least when the prompt is # you can always safely copy-paste the prompt, but there's historical circumstance to consider. in csh it's %

I've had several folks request that I remove the $ from documentation and just separate commands from output more clearly. I believe there is also a CSS trick you can do to display $ on the web but make it not part of the string you actually copy'n'paste.

Similarly, I've had folks request that long lines not be broken up with \ because that only works on macOS/Linux and produces "bizarre" behavior/errors on Windows.

> I believe there is also a CSS trick you can do to display `$ ` on the web but make it not part of the string you actually copy'n'paste. The ::before pseudo-element can do that: https://developer.mozilla.org/en-US/docs/Web/CSS/::before

.terminal-command-input-line::before {
  content: "$ ";
}

I don't think making it easy to do quick copy paste from a document into a terminal is actually a good thing. you should be putting more effort into reading the thing you are copying than it takes to avoid grabbing the $

Sure. You can tell that to beginners all you like but it won't stop them doing it 🙂

I'm just suggesting it's a "good friction"

Yes! What @U051SS2EU said. Copy and pasting into a terminal is a bad habit, similar to curl ... | sudo bash.

> ... just separate commands from output more clearly. This is a lot harder when you're documenting a back-and-forth command/response "conversation".

It works well in zsh, I decided to try it and in bash I went for :; to get the same functionality

I discovered that : works like a no-op in bash