Thanks, @GamzWithJamz. Color certainly can make things pop, and I've also personally spent quite a bit of [time](https://github.com/c-blake/lc) [tweaking](https://github.com/c-blake/procs) [colors](https://github.com/c-blake/hldiff) and have some generic support for run-time colors in [cligen](https://github.com/c-blake/cligen)/`humanUt.nim` that supplements compile-time stuff in the `std/[colors, terminal]`. Personally, I think human color response is variable enough that colors should be end user-configurable almost always.
I do think just asterisks and caps are probably enough in this case and a fully "display device portable eye pop". ;-) If you give up portability then blinking text is more or less impossible to not notice..Makes contact with our animal/hunter/prey motion tracking brains. Indeed, beyond portability the main objection you would hear would be " ** _too_** hard to ignore". Araq's release default idea might help with "I'm only used to interpreters" entry-level user, but honestly it will not be long before those people must learn to `-d:ssl` or do `--threads:on` or `--gc:arc/orc` or maybe now incremental compilation or whatever the fancy new thing of the day is. And even with his proposal, people will still misconclude "Nim is slow because of benchmark Y" because the author of Y in Nim didn't know Nim very well or the problem space very well or both. And as Araq also mentions, what `-d:release` even means, exactly, is not hard coded. So, the "default" could become more vague/ambiguous as well as not what other compilers do.
