The Curse of Markdown
A polemic arguing that Markdown discourages richer, more interactive web content has prompted debate over whether the real barrier is the format itself or how people choose to use it. Many commenters criticize the article’s own animated, scroll-driven layout as overengineered and less readable than plain text, seeing Markdown’s simplicity and HTML-escape hatch as a feature rather than a “curse.” Others counter that for complex technical, academic, or highly interactive documents, Markdown quickly becomes awkward, and they call for better tools or DSLs that blend ease of writing with richer presentation.
Scrolling UI and Readability
- Many commenters dislike the scroll-driven, paragraph-fading layout: text grays out at the reader’s natural eye line, makes it hard to look back, and feels like “slideshow” or “scroll jacking” even if technically it isn’t.
- Some find it unreadable on large monitors or mobile (blank space, delayed text, overlapping paragraphs, tiny fonts).
- A minority like the slideshow-like format and scroll-synced illustrations, but usually still object to greying previous text.
Charts, Data, and Visuals
- Several criticize the “plot-like” graphics as misleading: they look like data visualizations or bubble plots but are explicitly “made up,” blurring the line between sketch and empirical data.
- Others see the visuals as overcomplicated, flashy, and not adding much informational value.
Markdown’s “Curse” Thesis
- Many reject the idea that Markdown creates a harmful “gap” in richness: Markdown allows inline HTML and is often not the real limiting factor.
- Some argue the supposed web “wasteland” is actually a healthy boundary against unnecessary complexity and gimmicks.
- Others partially agree: Markdown alone is too limited for richer technical documents with figures, footnotes, programmatic content, and complex layouts.
Alternatives and Extensions
- Commenters mention richer systems (Pandoc, Quarto, Typst, Asciidoc, reStructuredText, custom Markdown forks, React-based setups) that bridge “lean” text and “rich” experiences.
- Several note that real constraints are build pipelines, standards fragmentation, and tooling complexity, not Markdown syntax per se.
Rich vs Simple Web Content
- Strong sentiment that “richness” often worsens UX: animations, cramped layouts, and heavy frameworks can obstruct reading and accessibility.
- Others defend richer, interactive pieces (e.g., advanced explorable explanations) as exactly the kind of content that needs more than plain Markdown.
Audience, Workflow, and Tools
- Debate over who Markdown serves: some say non-engineers overwhelmingly prefer WYSIWYG tools; others counter that lightweight markup is faster, more maintainable, and better with version control.
- Several see the article as over-engineered marketing for a new tool, with weak evidence that Markdown is significantly “holding back” ideas.