cm0002@lemmy.world to Programmer Humor@programming.dev · 1 年前No Connection, No Flushlemmy.mlimagemessage-square329linkfedilinkarrow-up11.44Karrow-down124cross-posted to: programmerhumor@lemmy.ml
arrow-up11.42Karrow-down1imageNo Connection, No Flushlemmy.mlcm0002@lemmy.world to Programmer Humor@programming.dev · 1 年前message-square329linkfedilinkcross-posted to: programmerhumor@lemmy.ml
minus-squarerekabis@lemmy.calinkfedilinkarrow-up1·1 年前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.
minus-squareDamage@feddit.itlinkfedilinkarrow-up1·1 年前It’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.