squirrel@piefed.kobel.fyi to linuxmemes@lemmy.worldEnglish · 3 days agoGUIspiefed.kobel.fyiimagemessage-square227fedilinkarrow-up11.27K
arrow-up11.27KimageGUIspiefed.kobel.fyisquirrel@piefed.kobel.fyi to linuxmemes@lemmy.worldEnglish · 3 days agomessage-square227fedilink
minus-squareprole@lemmy.blahaj.zonelinkfedilinkarrow-up1·19 hours ago Things like the parameter order mattering. I imagine this is unavoidable in many cases.
minus-squareJackbyDev@programming.devlinkfedilinkEnglisharrow-up2·18 hours agoYeah, I guess that’s true. I suppose given more time to think about it I wouldn’t really complain about that. It’s mostly things like script in out that are sort of annoying versus something like script --in foo --out bar.
minus-squarekunaltyagi@programming.devlinkfedilinkarrow-up1·18 hours agoI believe API (CLI or programmatic) should never have 2 arguments of the same type but different roles next to each other without visual cues. No fn("in.txt", "out.txt") and no script in out
I imagine this is unavoidable in many cases.
Yeah, I guess that’s true. I suppose given more time to think about it I wouldn’t really complain about that. It’s mostly things like
script in outthat are sort of annoying versus something likescript --in foo --out bar.I believe API (CLI or programmatic) should never have 2 arguments of the same type but different roles next to each other without visual cues.
No
fn("in.txt", "out.txt")and noscript in out