IMO / is used to distinct config sections from command arguments for better cognitive readability or just for ones who are used to / (or \) as directory separators in OS shells where in this case ROS config sections are represented as direcoties in ROS shell.
For eg. if you point terminal to /system script job, prompt will actuall separate sections with / which in this case will be [<user>@<device_name>] /system/script/job>.
Personally I prefer such syntax in my scripts /<section>/<sub-section>/cmd <arg1> <arg2>…
Good point that auto-complete includes the “/” which infers that Mikrotik are encouraging that format? Maybe switch on export to use the “/” character optionally? Although I’d still like to know the thinking behind the change in syntax.
Exactly, like users must do until a true working v7 exist, v6 is only the long-term for production.
Not all frills on v7 are for productions, are just tous for play at home.
I have v7 on some edge routers, but after too much kernel failure, mysterious reboot & co.
I search again v6 machine and I've made a decent supply of them, which I hope will be enough until they make a truly stable v7.
I’m not in the big installation market - I work in consumer and SOHO. One of my sites has an ancient RB2011UiAS in a very busy bar with four cAP ac APs. Just noticed that it’s been up for nearly a year on v7
I think a switch on export would be helpful in the transition to “/” separator?