Hang on still angry at this:

>A good UI should guide the user and reveal relevant information only as it's needed.

Ok so 99.99995% of all Mikrotik RouterOS devices do not end up in peoples labs.

Even the devices that are homeish in capability are mostly deployed into apartment buildings as NTD's and managed via API/Ansible not by the occupant.

The cheaper routerboards, like the 2000 series, are almost entirely eaten by Wisps.

When you configure a new RouterOS device the use case is non obvious.

It might be an edge router that needs BGP to be stood up first.

It might be a tower router that needs only OSPF, or full stack BGP/OSPF/MPLS.

Maybe its going in a data center to terminate a bunch of VPLS tunnels or VPNs.

It might be an NTD/NTU or it might be a bodgy relay.

I had a customer that would deploy small form routerboards as ethernet regenerators when doing really dodgy cabling.

You are not the target customer. Its cool and good that as a hobby you dipped your toes in. But its a very long stretch to turn around and complain that the interface isn't good enough because it doesn't hold your hand the way you would like it to. Mikrotik offers training and certification for people who cant work it out.

This is the networking version of raising a fault with the linux kernel because you don't want to compile it, you just want the exe.

And no, theres not a potential solution in Mikrotik having a separate code base for non technical people. They cant manage the code they already have. "Its coming in ROS7" was a meme for the better part of a decade. We are almost completely done with "This feature doesnt work on this CPU" which plagued them for ages.

Asking RouterOS to be more like DLink or whatever it is you are more comfortable with is insane and I hope fervently you never encounter JunOS which is the absolute godlike gold standard but will likewise not hold your hand to help you setup your DHCP config.