they86
Hi there….couldn’t agree more about the versatility color would bring.
I won’t presume to speak for the devs, but I can’t imagine that Legend’s use of markdown files" prevents the use of color text (natively or otherwise). I believe Dynalist was based upon markdown (I’m not certain about Workflowy), and they both have pretty versatile color text. In fact, being locked into markdown made the editors very non-wysiwyg for a long time. I’ve never seen that type of annoyance from Legend.
I would think that color, like headings, highlighting, item types, and a myriad of other things that Legend already has is just as possible (obviously, once the devs deem it feature worthy enough to implement). The more I think about it, Legend’s headings and highlighting seem like they’re 75% of the way towards a text/background color feature.
I agree with you about the hype about markdown…..if one more person tells me how human-readable it is (or JSON, or XML, or SOAP, or HTML, ad nauseum) I’ll puke. Latin is human-readable too, but not if you don’t learn it 😉
I don’t particularly care so much about the format of the object-based data the devs use. They could store it in Klingon as far as I care–as long as no one can say "we’re limited by our choice of <fill in the blank>. If the datatype is a limitation, then yes, the limitation should be removed. Legacy is a heavy weight to drag around every day in code, to be sure.