All the annotations are optional :P You can have a super terse definition.

In my current experience it helps me throw a CLI config into an existing service in ~0 time (e.g. set number of workers, modify port/host, etc.), so I try to minimise the LoC-to-result metric.

Good luck with your macros :)

I'm a big fan of Decline, but I still think that leaving macro-derived CLIs off the table is incorrect – you can get quite far with enums, case classes, and annotations in small to medium apps. In my projects I use both the raw Decline API and my own derivation mechanism for it.

Ugh, I was hoping to avoid learning any new kubernetes concepts for my server

There are limits to this of course, but long term committment to a behaviour that is no longer correct/doesn't align with the vision of the interface and its contracts doesn't serve the maintainers or the majority (sic!) of users

I think it depends what you define as compatibility (and IMO it shouldn't be an all encompassing "this will never change promise"). In my area where compatibility is defined by binary and syntactic vectors, a prominent maintainer responded to exactly such a question: github.com/typelevel/ca...

But the good thing is that once it works (after trial and error) it continues to work in different environments, and you have a single file with a blueprint of what it takes to build the app on a clean machine.

Using a slightly more portable DSL than GH workflows

Probably the most horrific application of this approach is in sn-bindgen-web: github.com/indoorvivant...

Copying individual linux and llvm files, publishing 6 different forks into local cache, installing system AND vcpkg dependencies... It used to build NGINX Unit from source!

Code (and details) are here: github.com/keynmol/scal...

It makes each platform infinitely more boring, thus reducing the desire to check it again and again in doom scrolling death spiral, but after gigabytes of rage bait and O-faced thumbnails I've given up.

It's probably the wrong thing to do, but after the horrors of For You page on Twitter I've sworn off any algorithmic timelines.

On Twitter I use addons.mozilla.org/en-GB/firefo..., on Bluesky I just don't open Discover, on Youtube I live on my Subscriptions page.

Because they had licorice in them, yes.

I respect you Noel but honestly, fuck licorice. Fuck it straight to hell.

I didn't know anything about Electron or any of its tooling prior to this, and the journey wasn't particularly smooth.

Electron bindings were really the only Scala-specific hurdle, the rest was JS tooling/Electron related.

Very satisfying to get something that finally works!

github.com/scala/scala3...