I think that how to manage and load Mikrotik staff is out of our business
so, this topic, what does it exist for?
Firmware staff could be different from winbox staff, so nobody subtracts time to nobody.
If winbox is to execute the RouterOS code ( «cannot run RouterOS code» ), surely it also needs to interact with other parts, not just the "nice" script editor,
so that already belies the fact that "it only takes one person",
then there are dozens of things that winbox (and also webfig) that they don't do and that are only available via CLI,
so it's better if, as already written, they finish before developing what they have to do to make winbox do everything that is already available.
Your preferred editor cannot run RouterOS code. So it's not the same.
why, writing an "editor" for winbox would it "compile" and "execute" the script before running inside the routerboard?
Do you ever wrote a complex huge script?
well... who knows... just some hundred... ask the others forum members...
If colorize the script editor is useless, why is the terminal colorized?
For the same reason you can open any topic on this forum and add it to the hundreds of useless topic
about requests made to forum users (instead of staff) that mikrotik personnel will never consider.
Even the scripts give such generic errors that often you don't understand what's wrong,
dozens of instructions are absent, like a very stupid "search and replace",
the floating point numbers are missing,
the time and date is inconsistently written in 4 (and more) different ways,
the conversion functions are trivially missing,
already working function are broken and never repaired (like convert a string to ip-prefix)
directory can not be created
the variables are limited to 4k or 62k (depends on case and context)
missing CP1252 (and the other), UTF-8 and UCS-2 support
and I could continue the list for hundreds of other things,
let alone if they are dedicated to "coloring" the code, as if it were the most important thing to do....