In the brave new world of letting non-distribution-maintainers look after software distributions (npm, crates.io, pypi, etc) containers seem like one of the only safe ways to isolate them from everything else. I don't even want my base OS contaminated.
Is this a religious objection to containers in general, or just to the common container technologies such as Docker? The latter I can understand, the former not-so-much.
I have been told it's manageable if you relegate it to a container and try not to touch. It's bad enough as a user, I dread to think what it's like for a sysop.
I remember Prolog from uni. My programs were always so bad they either said "Yes" or overflowed the stack. Getting a complex Prolog program to say "No" never worked for me :(
After a weekend of hacking on React web UI thingies (thanks @suchconor for the help to become confident in it) I can safely say I'm now "full stack" (anything from VHDL, board layout, firmware, bootloaders, kernels, system-software, app software, and web-UIs)
Can the excavator already extract lapis/redstone in a trad. world? If so, what does it do? Give you blocks, or items? If items, is this hard-coded or calculated as the drops from the blocks?
Hey @monzo here's another #extraordinaryidea
When setting up and/or modifying a standing order or direct debit, being able to nominate a pot to try before using balance would aid greatly in budgeting.
Hey @monzo, here's my #extraordinaryidea
With an API to manage pots, someone could write a tool which would watch transactions, automatically maintaining pots based on rules the owner of the account can define. (e.g. maintain between 50 and 100 available using pot "spare")