|
|
|
|
|
|
by w10-1
563 days ago
|
|
|
This doesn't back the hypothesis that there are applications (cough opportunities) held back by markdown's deferral of styling. Markdown's chief feature is to be usable without tooling when writing, so more content is generated in the first place. So it extends the rich/cost graph to the left. Because markdown is easily and often parsed, it operates as a data source from the get-go, mostly achieving the separation of concerns needed to scale to the right. What are the pain or price points that will change with adopting this new technology? (Is Swift-docc really the comparable? It seems to show what this is hopefully not: a subset dialect of markdown struggling with volatile, unusable hash links, no real extensibility or inter-op, tethered to BigCo's mission.) (The curse of curses: they provoke negativity.) |
|
|