Thanks for your comment. It totally makes sense.

Sometimes, it is the art of balance. As a product, the goal is to save users time as much as possible. Eventually, the users have to decide whether it's appropriate to put a super complex table in Markdown, although it will be fine for tables with short rows.

While I'm writing this reply, I thought of how to improve this in Document Node. It can automatically check and add padding depending on whether any Markdown rows exceed 80 characters (or similar). One less thing to worry about.