IdeaWell

Project ideas from Hacker News discussions.

Why are we still using Markdown?

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

Three prevalent themes in the discussion

  1. Prefer simplicity and low‑friction writing
  2. “Because, like UNIX/Linux itself, worse is better: … Markup is overhead. Markdown is the best compromise we know of today that provides just enough structure while imposing very little cognitive load.” – otterley
  3. “i use it because it does what i want and is easy to use.” – fl4regun

  4. “Because I think it’s fair to say it’s becoming a standard format for AI agent specs docs etc. It’s not going anywhere anytime soon.” – andersco

  5. UI/UX shortcomings hinder usability

  6. “This website, at least in dark mode, doesn't have any visible indication when text is selected … the links at the bottom aren't actually links (so you have to select them to copy and paste into your address bar).” – sethherr

  7. Skepticism toward theoretical solutions without concrete implementation

  8. “When I read articles like this my reaction is always ‘put up or shut up.’ If you have a better idea, make it happen. The author merely described the parameters of a solution and didn’t even attempt to solve it.” – dangus

🚀 Project Ideas

Generating project ideas…

MarkPulse

Summary

  • A CLI linter/formatter that enforces consistent Markdown syntax to eliminate ambiguity and reduce cognitive load.
  • Provides automatic conflict resolution for common ambiguities (e.g., emphasis markers, list symbols).

Details

Key Value
Target Audience Technical writers, open‑source maintainers, documentation teams
Core Feature Auto‑linting and auto‑formatting with enforced syntax rules and conflict resolver
Tech Stack Node.js, markdown‑it, Prettier, CLI
Difficulty Medium
Monetization Hobby

Notes

  • HN users repeatedly cite the “cognitive load of deciding between asterisks vs underscores” as a pain point.
  • Solves the need for a “clean yet expandable syntax” that still feels familiar, echoing Typst’s consistency principle.

ZenEdit

Summary

  • A minimal web‑based Markdown editor that offers context‑aware auto‑completion and optional WYSIWYG mode to lower entry barriers.
  • Merges live preview with plain‑text source persistence, reducing the friction highlighted by users who dislike invisible formatting.

Details

Key Value
Target Audience Developers, note‑takers, content creators seeking low‑friction writing
Core Feature Context‑aware syntax suggestions and toggleable WYSIWYG editing
Tech Stack React, Monaco Editor, AI suggestion engine (e.g., OpenAI embeddings), Tailwind CSS
Difficulty Low
Monetization Revenue-ready: $5/mo subscription

Notes

  • Directly references HN praise for Obsidian’s “WYSIWYG markdown editing” and the desire to “eliminate that cognitive load.”
  • Addresses the conflict between “I don’t like WYSIWYG editing, as it makes the formatting invisible” and the need for readable source.

ConsistMark

Summary

  • A stricter, unambiguous subset of Markdown with a well‑defined rule set, plus a validator and auto‑formatter.
  • Turns the “Markdown is a mess of dialects” complaint into a single, predictable syntax for teams.

Details| Key | Value |

|-----|-------| | Target Audience | Engineering teams, wiki maintainers, anyone needing consistent documentation markup | | Core Feature | Strict syntax (e.g., only underscores for emphasis, hyphens for lists, explicit link brackets) with validation and auto‑format | | Tech Stack | Rust, pulldown‑cmark, WebAssembly, CLI | | Difficulty | High | | Monetization | Hobby |

Notes

  • Echoes HN sentiment that “Markdown tried very hard to encode conventions that were already used in Usenet, email…”, aiming to formalize those conventions.
  • Offers a concrete solution to the “many ways to do the same thing” problem, appealing to users who want a “clean yet expandable syntax.”

Read Later