🚨The security blog by #Google
is true gold!

🚀🥳It really helped me to learn more about software supply chain security things including #deps.dev, #go, #SLSA, #SBOM, #scorecard, #distroless, and many more!

🧑🏻‍💻I highly recommend you take a look at this blog!

https://security.googleblog.com/2023/04/celebrating-slsa-v10-securing-software.html

lein2deps now comes with a leiningen plugin to automatically sync your project.clj to a deps.edn:

https://github.com/borkdude/lein2deps#lein-plugin

#clojure #deps #leiningen

On the other hand, the resolvers depending on themselves is going to be a little trickier.

If this was a compiler, I'd just keep around the last binary, and use that to build the rest.

But in this case, we built these resolvers with warp, using an older version of themselves that vendored everything. But now during the resolution process of the resolvers, we need them running!

Easiest option seems to be *vendor deps* at this level.

#deps #elixir #erlang #latebinding

Comment appliquer automatiquement des modifications sur une codebase JS 🤖 https://tech.bedrockstreaming.com/refactorer-avec-jscodeshift #javascript #refactor #update #deps

@codesections I just got around to reading both your posts. Personally I'm very much on the "minimise deps" side, so I like a language with a good standard library. And I think there exists some optimum between #deps and dep size.
The "fits on a screen" criterion makes sense too.

Your _ sounds like a very good supplement to the standard library. Self/Recursion is a bit the odd one out, but obviously the one that caught my attention. I didn't even know Raku had &?ROUTINE.