Re:If it is worth keeping, save it in Markdown
by assimpleaspossi on Tuesday February 25, 2025 @09:12PM
(#43179867)
Your complaint seems to be about the editors, not HTML.
Re:If it is worth keeping, save it in Markdown
by pimlottc on Tuesday February 25, 2025 @11:02PM
(#43180469)
Unless you're willing to write your own editor, that's not really a practical distinction
Re:If it is worth keeping, save it in Markdown
by dangus on Saturday March 01, 2025 @09:47AM
(#43219698)
Yes, my complaint is about the editors. But it's also a problem with HTML because with HTML you can implement a document that looks the same using multiple techniques, so editors will always have code generation differences.
Re:If it is worth keeping, save it in Markdown
by hakaneskici on Tuesday February 25, 2025 @08:56PM
(#43179793)
Makes sense. I was thinking that browsers have native support for WYSIWYG editing and most browsers/apps are Chromium based; so how the browser handles HTML formatting should be stable for a single person scenario even across apps.
Re:If it is worth keeping, save it in Markdown
by oneeyedpigeon on Wednesday February 26, 2025 @05:31AM
(#43182497)
HTML isn't "horrible" at WYSIWYG, it just isn't WYSIWYG. Your comment is like saying "JSON is horrible at for loops"βit's just a misunderstanding of the tool.
If your editing tool changes or if your switch editors, they will all botch your HTML anywhere you make edits.
RTF is basically "it just works," very much like "Microsoft Word Light."