Last call! Two more days to send in a talk proposal for a full or lightning talk for Babashka Conf 2026! babashka https://babashka.org/conf/#cfp Thanks to Nubank, Exoscale and Bob for sponsoring the conference! New update: we have found our event host / MC / speaker liaison: @mrswendyrandolph all the way from the US! (We are looking for one last sponsor to cover the costs and to be able to provide a snack during the coffee break! ❤️ )
Any plans for 1.12.216? I'd like to try out some of the recent fixes, but don't have GraalVM to build from src
you can always try out the version from master with:
bash <(curl ) --dev-build --dir /tmp I'll give that a try. Thanks!
Idea for babashka.fs: Would a lite implementation of the key features of touch(1) be useful? Sure, one can write a bespoke function each time, but it seems something useful enough to capture in the library
On the topic of shooting oneself in the foot with symlinks. Never make a backup with cp -r 😬
something like:
(defn touch [path]
(if (fs/exists? path)
(fs/set-last-modified-time path (System/currentTimeMillis))
(fs/create-file path))
path)
?With an optional second argument to choose a specific timestamp (defaulting to the current time)
and creating the file when it doesn't exist?
I would probably use a multiple-arity function.
symbolic link behavior should also be specified: change the link itself or the target
That's one reason to keep it lite. Maybe whatever the underlying function does by default
in my experience this should be fully spec-ed out. it wouldn't be the first time that I shoot myself in the foot by not thinking about symbolic links. Github issue welcome with all the details
I'll try to get it posted soon
Why should this create the file if it does not exist?
it's the standard touch behavior I guess.
the problem of this thread is that people have different expectations of what a touch -lite is, so "can you just add it" isn't going to happen unless someone fully specs it out
I have definitely written this fn 🙂