> extend our RST parser ouch. this sounds like a maintenance nightmare / time sink, for several reasons:
* it needs to be developed, debugged and bugfixed - not only the code, but the spec of the format as well! * downstream developers of tooling etc need to adapt to it - this is a _[huge](https://forum.nim-lang.org/postActivity.xml#huge) cost - is this really the highest priority that we want tooling developers to spend mindshare on? * users will be confused, and much time will be spent by the community explaining these differences, again at the cost of other things Nim that don't get done. all in all, nim has a small community and limited resources - using a standard for certain things will buy time and resources to advance the other things that makes nim an great and interesting development - develop its strengths - is developing a "better", high-quality markdown alternative really a goal for project?
