nrepl

mkvlr 2024-08-30T14:55:50.648249Z

hey, I’m wondering if there’s already a naming convention in use for naming nrepl socket files? Something similar to .nrepl-port but supporting more than one and giving them a name? This https://mastodon.online/@nikitonsky/113050603764542757 from @tonsky sums up the potential benefits of unix domain sockets over ports nicely.

bozhidar 2024-08-31T11:28:56.512659Z

There's no naming convention in place today, but I guess something like nrepl.sock kind of makes sense. 🙂

bozhidar 2024-08-31T11:29:33.592119Z

The main reason it took us forever to implement this in nREPL was that older JDKs didn't have support for Unix sockets. Windows didn't have support for them as well, before Windows 10.

bozhidar 2024-08-31T11:29:48.326519Z

So we had to wait a very long time for the stars to align in our favor. 🙂

mkvlr 2024-08-31T12:04:26.885599Z

I’d prefer a naming convention that can deal with multiple REPLs, so e.g. Clojure.nrepl-socket or shadow-cljs.nrepl-socket

mkvlr 2024-08-31T12:04:56.549259Z

being able to use the filename for the REPL name would be nice I think