@[email protected] to Programmer [email protected] • 15 days agoNo Connection, No Flushlemmy.mlimagemessage-square335fedilinkarrow-up11.44Karrow-down124cross-posted to: [email protected]
arrow-up11.41Karrow-down1imageNo Connection, No Flushlemmy.ml@[email protected] to Programmer [email protected] • 15 days agomessage-square335fedilinkcross-posted to: [email protected]
minus-square@[email protected]linkfedilink1•13 days 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•12 days 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.