362 karma · joined September 13, 2010
> But personally, I don't use tell-dont-ask. I do look to co-locate data and behavior, which often leads to similar results. One thing I find troubling about tell-dont-ask is that I've seen it encourage people to become GetterEradicators, seeking to get rid of all query methods.
For anyone surprised or unfamiliar, that’s the weight of an entire box with 8-10 frames, not the weight of a single frame—while that’d be delightful in terms of honey production, it’d be miserable when doing hive checks, etc.
Thank you for all the time you’ve taken to explain the “why” of Erlang!
(For those unfamiliar, go check out “The Erlang Rationale” and some of rvirding’s posts elsewhere, e.g., on the thread at https://elixirforum.com/t/the-erlang-rationale-by-robert-vir...)
(I’m a beekeeper in the US, so Varroa is something I’m unfortunately too familiar with.)
That said, I’d much rather deal with Varroa than AFB any day as it stands today. The current required action for AFB in my area is burning the entire hive including the woodenware. A vaccine to prevent AFB would be fantastic, as it’d remove the one thing that I’m actually concerned about from getting into my apiary.
Perhaps I missed it, but I thought [Semantic Versioning](https://semver.org/) required a “-“ between the patch number and a prerelease identifier since at least version 1.0.0 (with 1.0.0-beta allowing a “.” instead of a “-“), no?
I don’t think Elgato, the manufacturer of the Stream Deck, or this guy, who wrote code to integrate with it, have anything to worry about.
op get item <name or UUID> | jq '.details.fields[] | select(.designation=="password").value' | sed 's/"//g' | pbcopy
will put the password for <name or UUID> on your clipboard on a Mac. (I'd probably wrap everything before `| pbcopy` in a function so it's easier to call and use directly if you don't want to copy the value)