Apple. Apple Please

#1

Post by ciclotrone » Sat, Aug 10, 2024, 6:14 PM UTC

Re: Apple. Apple Please

#2

Post by kevingadd » Sat, Aug 10, 2024, 6:48 PM UTC

The way they disambiguate between the two options feels like it would have been a ton of work to figure out and implement... and for what purpose? I don't understand the user story here. How hard is it to type the long version?

Re: Apple. Apple Please

#3

Post by dangus » Sat, Aug 10, 2024, 6:51 PM UTC

You know, I think this is oddly clever. Maybe it’s dumb but it seems like it appeases typical user habits.

Re: Apple. Apple Please

#4

Post by MOARDONGZPLZ » Sat, Aug 10, 2024, 6:51 PM UTC

kevingadd wrote: post #2

The way they disambiguate between the two options feels like it would have been a ton of work to figure out and implement... and for what purpose? I don't understand the user story here. How hard is it to type the long version?

As a user, I don’t want to have to type the full option name every time I use it.

Re: Apple. Apple Please

#5

Post by OsrsNeedsf2P » Sat, Aug 10, 2024, 6:51 PM UTC

I think it's clever that Apple uses the `-v` flag for both verbose and verify options. It streamlines the command-line interface, keeping it simple and easy to remember. Apple's software is designed to interpret context, so it effectively handles both functions without confusion.

Re: Apple. Apple Please

#6

Post by nerdponx » Sat, Aug 10, 2024, 6:54 PM UTC

MOARDONGZPLZ wrote: post #4

kevingadd wrote: post #2

The way they disambiguate between the two options feels like it would have been a ton of work to figure out and implement... and for what purpose? I don't understand the user story here. How hard is it to type the long version?

As a user, I don’t want to have to type the full option name every time I use it.

GNU solved this problem a long time ago by distinguishing -v and -V.

Re: Apple. Apple Please

#7

Post by tpush » Sat, Aug 10, 2024, 6:55 PM UTC

OsrsNeedsf2P wrote: post #5

I think it's clever that Apple uses the `-v` flag for both verbose and verify options. It streamlines the command-line interface, keeping it simple and easy to remember. Apple's software is designed to interpret context, so it effectively handles both functions without confusion.

Is this satire?

Re: Apple. Apple Please

#8

Post by collingreen » Sat, Aug 10, 2024, 6:58 PM UTC

MOARDONGZPLZ wrote: post #4

kevingadd wrote: post #2

The way they disambiguate between the two options feels like it would have been a ton of work to figure out and implement... and for what purpose? I don't understand the user story here. How hard is it to type the long version?

As a user, I don’t want to have to type the full option name every time I use it.

As a user, I want to feel in control of the behavior and be able to learn through doing because the output is reliable. I do not want to have to guess what is going to happen nor do I want to be surprised that a command has different behavior than last time I used it.

Re: Apple. Apple Please

#9

Post by quantified » Sat, Aug 10, 2024, 6:58 PM UTC

tpush wrote: post #7

OsrsNeedsf2P wrote: post #5

I think it's clever that Apple uses the `-v` flag for both verbose and verify options. It streamlines the command-line interface, keeping it simple and easy to remember. Apple's software is designed to interpret context, so it effectively handles both functions without confusion.

Is this satire?

It looks LLM-generated.

Re: Apple. Apple Please

#10

Post by happytoexplain » Sat, Aug 10, 2024, 6:59 PM UTC

OsrsNeedsf2P wrote: post #5

I think it's clever that Apple uses the `-v` flag for both verbose and verify options. It streamlines the command-line interface, keeping it simple and easy to remember. Apple's software is designed to interpret context, so it effectively handles both functions without confusion.

I'm not entirely sure if this is sarcasm or not, but "clever" is commonly cited as something you don't want APIs/UIs to be.