@[email protected] to Programmer [email protected] • 1 month agoNo Connection, No Flushlemmy.mlimagemessage-square334fedilinkarrow-up11.43Kcross-posted to: [email protected]
arrow-up11.43KimageNo Connection, No Flushlemmy.ml@[email protected] to Programmer [email protected] • 1 month agomessage-square334fedilinkcross-posted to: [email protected]
minus-square@[email protected]linkfedilink1•1 month agoWill have to look into that, thanks. One of my key implementation requirements, however, will be resiliency, which means simplicity will be a core feature. The more “moving parts”, the easier it will be to break.
minus-square@[email protected]linkfedilink1•1 month agoIt’s not easy to make it any simpler. You’ve got to control those devices somehow.
Will have to look into that, thanks.
One of my key implementation requirements, however, will be resiliency, which means simplicity will be a core feature. The more “moving parts”, the easier it will be to break.
It’s not easy to make it any simpler. You’ve got to control those devices somehow.