4 ms·
Have you read the documentation for this beast? It is complete but I would not describe it as easy to use. To be fair, we could probably slap an API and a GUI
by gerdesj 6y ago
Have you read the documentation for this beast? It is complete but I would not describe it as easy to use. To be fair, we could probably slap an API and a GUI on top of this nonsense:
$ burrito -time +:30 b+g+cc+jf+jf+sf+sc-sc+i"Black Beans"+n:2/Ross \
b+v:cc+g+cm+sc+i"no rice"/Kathie
(sigh no double dash long options and a horrific base food specification thingie - yes it is complete and well formed but it is still bollocks:
FoodSpec::=<type>[options*][/<name>]
<type> ::= [b|t|m|q|T]
(burrito, taco, mexico city, quesadilla, Taqitaco)
)
RLY? Even in 1992 RAM was not too scarce. There was no reason to be so compact in form. If it was then those + symbols can go and better choices of options made to avoid ambiguity.
- Nextgrid 6y agoIt is complex, but the advantage is that once I have the command figured out I can save it as an alias and be able to invoke it in seconds.
- arp242 6y agoAt least it's something you can work with: write your own interface against, program an UI on top of it, or whatnot. Now I'm stuck with whatever crappy interface the Grab and Gojek developers give me on my shitty mobile phone (imagine people wanting to use their 1920x1080 screen instead of a phone to order food...)
- rdtwo 6y agoIt’s because the phone serves as another small layer of fraud protection
- ac29 6y agoThere was a GUI... named, of course, xburrito: http://plinth.org/techtalk/?p=81 http://plinth.org/techtalk/?p=81