News for hackers. Stuff that matters.
Re:If it is worth keeping, save it in Markdown by nicoburns on Tuesday February 25, 2025 @09:38PM (#43180008)
It's not sarcasm. HTML is and always has been a decent format for hand-authoring documents. It's not as nice to use as markdown, but it does support more advanced use cases like coloured text.

And if you want an "archival" format that will stand the test of time it's pretty good (so long as your text encoding is readable, HTML will be).

Re:If it is worth keeping, save it in Markdown by colonial on Wednesday February 26, 2025 @12:50AM (#43181045)
I agree with you, but I will say that Markdown (or at least, all the major "standards" for it) support interleaving HTML both inline and at the block level. Unless you are writing a very bombastic document or want to avoid a rendering step, I'd argue that you'd be best served by just writing CommonMark with embedded HTML.
Re:If it is worth keeping, save it in Markdown by oneeyedpigeon on Wednesday February 26, 2025 @05:34AM (#43182515)
I'd argue that, at that point, you might as well write HTML. I find it easier to work with one format at a time rather than two intermixed and a typical Markdown document is barely more readable than its equivalent HTML document, while the latter gives you a lot more flexibility and semantic accuracy.
Re:If it is worth keeping, save it in Markdown by cma on Wednesday February 26, 2025 @03:32AM (#43181893)
versus markdown it is ungreppable with all the escape codes/entities, then you have to use special tooling for search.
Re:If it is worth keeping, save it in Markdown by oneeyedpigeon on Wednesday February 26, 2025 @05:35AM (#43182524)
Avoid character entities—store your HTML files as UTF-8 and just embed everything.
Re:If it is worth keeping, save it in Markdown by cma on Wednesday February 26, 2025 @03:33PM (#43187887)
I guess that mostly works but lots of my notes have <>'s. I guess <code> covers most of that