Now that I’m trying to work with the API, this seems like a dumb question. Checked exceptions are too burdensome.
@qbit now that I’m actually trying to use it, I think you’d want to avoid LockInterruptably in pretty much any business logic. It throws a checked exception. That’s also kind of weird (seems like a user interrupt is a clear runtime exception to me).
Changelog was kind enough to feature my recent post on semantic versioning:
Incidentally, I had been reading nobs(1) as "knobs," but I understand now that it should be pronounced "no-b-s" (bs for backspace, but one could think of more creative expansions).
Adding a second DoT provider to my forward zone seems to have resolved things:
I got upset enough to write a post about it.
OpenBSD hackathon #k2k20 started. deraadt committed the associated picture
(I am not at k2k20)
The right strings arrangement will bring me to tears https://www.youtube.com/watch?v=27Zz-RP9vi0
Just timed a full build-and-test in Go at .95s. I’ll need to re-implement this in Java anyway, so I’ll be curious to see what the time run returns there.
I might be speaking too soon, because my reference is ~30s to run a full build and test with Maven, whereas 5ms in Go is just the test. So not an apples-to-apples comparison.
Software Engineer. Adjunct Professor. Christian, husband, and father. Opinions are my own. Aphorisms are experimental. he/him
A private Mastodon instance