Surprising changes in RouterOS7 cli vs RouterOS6 cli

[szymonc]

Mrz, thank you for reply. Please do not take critics about one feature as critics over whole device/company etc. Mikrotiks are great anyway, but…

@mrz

Unfortunately, this “surprising change” exist already for several years.

I’m working with Mikrotik devices for at least 3 years now. The ones used in production environment, sorry we do not go for testing branch very often, we also rather avoid stable and stick with long-term (to avoid e.g. missing routing tables problems or at least to gain awarenes). The only reason we went for stable 7 was to check the limits for smaller devices we prepare for our customers, hence surprise. We are in no way network device developers, we just use them, and use them a lot, stability is our main concern.

@mrz

Since then there were only a few users who did not like the change and some even liked the new method.

I would say, perhaps most heavy weight users are going to discover it when they arrive to ROS7 with its first long-term release? Early adopters tend to be hyped about new features and usually don’t care for little nuisances of everyday mundane tasks present in production environments. (Highly speculative opinion, based on my own and coworkers experience, prove me wrong but please do not jump on me.)

@mrz

You are not forced to use spaces, nor slashes, use whatever method suits you.

In a fact I am. Autocomplete with - I got slashes, default prompt with “path” - slashes… is there a switch/option to change it? Must have missed it.

@mrz

The old input method with spaces is not removed and will not be removed because of the exact reason that some users might not like typing slashes.

Glad to hear it, but this somewhat contradicts my suspicion that the goal is to have one parser for cli and api and still raises my curiosity: Then why?