dissoc?

How could I!?!?! Of course

Well, to be fair they have different signatures! dissoc is variadic, so I suppose you could make a but-keys that apply dissocs the keys from the map

(defn but-keys [m ks] (apply dissoc m keys))

Yah, but dissoc is more than enough 🙂

I love these “but of course!” revelations you get in Clojure-style functional programming

I was just confused by some code that didn’t use dissoc and had a liberal use of select-keys so my brain just thought but-keys

naturally

(also, would be symmetric with last and butlast

I believe there is room for a penultimate fn though

(def penultimate (comp last butlast)

haha

what about nth-last ???? I NEED IT.

and I have a use case for rest-but-nth-last

it must be hard to decide which functions to include. Took them 15 years to add update-vals and update-keys

even though every single Clojure programmer probably implemented similar fns themselves

Even though the names can be a bit confusing in their irregularity at times, I really respect Rich for assembling a coherent and succinct core. And, after I passed the newbie stage, I certainly see the value in keeping the core small, instead of trying to include everything and the kitchen sink.

and the core isn’t even that small…

isn’t it more that the inclusion criteria are so strict that hardly any fluff ever gets added

any function needs to wax on/off Rich Hickey’s car for 10+ years before it even gets considered

🥋

can’t believe that emoji exists

I’m guessing you can take all of these beautiful morning shots because you’re out walking your dog every day?

just myself these days, long story

I usually use rsync for this - more resilient .. probably

if it had failed yes... but this worked remarkably well.

cool! the servers I’m dealing with are too flaky for loooong scp transfers, even normal ssh keeps breaking so I use mosh

I think the two server are in the same data centre, maybe even in the same rack.

hence the high transfer speed

might well do

that was quite common in the olden days,

If I were working on a cloud project, I would just publish the logs to Cloudwatch or whatever. But since I’m not, and I’m hesitant to introduce something like Logstash etc. because of the operational overhead. I wonder whether this would make for a lightweight solution for queryable logs.

Could just expose a socket server (via SSH only) to allow developers to run whatever log queries they want via the REPL. And prepare a few helper functions for common queries.

I mean I think it would be an improvement over desperately grepping strings, but… 🤷

Some prior art: https://github.com/ont-app/graph-log

Thanks! I’ll take a look at that.

there are datascript and a datomic bindings, but so far nothing for datalevin

@UB3R8UYA1 is usually pretty open to suggestions and/or PRs though 🙂

Personally, I have no idea whether logging to a triplestore is a good idea, but I’m certainly intrigued by the concept 🙂

This is what some other people use logstash for right? Dumping JSON into ES and then querying that

Yes, I mentioned Logstash above.

oh yes, oversaw that

One thing I found at some point was that a lot of things not exposed directly as functions from java.time are exposed as a map by calling t/fields on a date. That’s how I found that getting the week number is not all that difficult.

thx for the tip on t/fields

there is a lot of magic in interval stuff as well, which I need to use a lot. I've done at least one complicated function that I think I can replace with concur