Let me demonstrate a rather Catastrophic Flow fail with an example taken from recent article work I was involved in. Rather than nuke this message board, I'll link you to a test Flow board where I posted it:Example: Flow Fail
Here's the Article Talk page that the example came from. That table is BIG, but the Talk interface is perfect. You can view that table exactly as it would appear in the article. You can view the entire contents of the table just by slowly dragging the browser scroll bar down. Or using just a mouse wheel. Or by simply clicking the scroll bar several times going down page by page. Or similarly by tapping the PAGE_DOWN key several times. In Flow that table is mangled beyond recognition because the Flow "low density interface" is too narrow for editing work. Trying to view that table in Flow means battling the interface. Fully viewing the table contents in Flow requires anywhere from fortyish to several hundred mouse-actions, constantly switching between the browser vertical scroll bar and the Flow's horizontal&vertical scroll bars. Try it, and count how many separate mouse actions it takes to view everything, row by row. And don't overlook that you have to Flow-scroll-right to see the text column on the right.
I haven't be able to find up yet what scratchpad is supposed to be... maybe that table should have gone inside a scratchpad? I have no clue. Was scratchpad planned to be full width? (Matching current Article and Talk Width)
Support that table, at full width, with multiple people editing it. If you want Flow to replace Talk pages for editing discussion and work, that's what we need. A collaboration and work system, not just a beautiful message board.