I think it's much quicker to apply a few checkboxes than to edit a text file in hex. If you really want, you can make some 10-20 standard configuration backup files and then just upload them. Much quicker than editing.
(I don't think anyone wants to edit a hex file, although I have used Hex Workshop for years, ascii is OK)
Here's my long winded problem with the SwOS config files:
I install networks that are usually remote. I am not there, there is no "IT guy" there.
I ship equipment to the site to save shipping costs. I design the networks and re-use configs as much as possible.
I "kit up" the job by emailing or posting to a website all the device configs:
"Bob here's the configs for the Sunshine Ranch project"
Bob knows how to get the configs into the devices.
My field techs are good, but they are not network engineers. They are installers and very good at it.
They know enough and we have given them the tools to be able to unbox and then winbox/web/console/tftp/etc and install.
Fast, cost effective and excellent results.
I can almost script the install down to when and where each component gets installed and config'd.
As much as I like the idea of a low cost vlan capable switch, it will cost more in the long run if I can't have a field tech quickly paste a config file into it and screw it to the wall.
It's just that simple.
You might think that I could simply make the switch config sitting at my desk, but that is not feasible.
I will spend more in time setting it up (where is the power supply?) than it is worth.
With an [ascii] human readable text based config, I can cut and paste and have a config done in about a minute as I'm sure lots of others on this forum can. Once you work with configs long enough it is like the Matrix, you can read it quickly.
For ROS, I put a handful of variables near the top that I can change quickly: IP/GW/PW/ID
Once the main router is up, I can use it to tweak anything else.
This is a real scenario - for me at least. I'm a lean shop and I need my new install done fast and right the first time.
To sum it up, you gave us ROS that had winbox and rsc files and then took it away in SwOS.
SwOS configs are a step backwards as far as I am concerned. It is almost as useless as the bin config file for a consumer router.
Bad decision by MT for me and I expected something different.
Building a brand is a lot about consistency.