I find it kind of telling that customers are just getting around to complaining about it two years after it was released. Not at all surprising, but illustrates how slow network operators update cycles can be compared to the pace of development.
To the Junos developers, this is ancient news, long forgotten in the dozens of sprints and multiple releases since. On Wed, Jul 12, 2023 at 2:13 PM Andrey Kostin via juniper-nsp < juniper-nsp@puck.nether.net> wrote: > Hi Mark, > 100% agree if it could help. > Very annoying. If UX designer touched it, he or she probably never > actually worked with Junos. > > Kind regards, > Andrey > > Mark Tinka via juniper-nsp писал(а) 2023-07-12 04:49: > > So, this is going to be a very priviledged post, and I have been > > spending the last several months mulling over even complaining about > > it either on here, or with my SE. > > > > But a community friend sent me the exact same annoyance he is having > > with Junos 21 or later, which has given me a final reason to just go > > ahead and moan about it: > > > > tinka@router> show rout > > ^ > > 'rout' is ambiguous. > > Possible completions: > > route Show routing table information > > routing Show routing information > > {master} > > tinka@router> > > > > I'm going to send this to my Juniper SE and AM. Not sure what they'll > > make of it, as it is a rather priviledged complaint - but in truth, it > > does make working with Junos on a fairly historically commonly used > > command rather cumbersome, and annoying. > > > > The smile that comes to my face when I touch a box running Junos 20 or > > earlier and run this specific command, is unconscionably satisfying > > :-). > > > > Mark. > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp