A software engineer from Seoul. An advocate of F/OSS, fediverse, and cypherpunk. Hack into East Asian languages.
Node.js @programming.dev Fedify 2.0.0: Modular architecture, debug dashboard, and relay support
Fediverse @lemmy.ml Fedify 2.0.0: Modular architecture, debug dashboard, and relay support
Fediverse @lemmy.world Fedify 2.0.0: Modular architecture, debug dashboard, and relay support
TypeScript @programming.dev Optique 0.10.0: Runtime context, config files, man pages, and network parsers
Fediverse @lemmy.ml Hollo 0.7.0: Advanced search, faster notifications, and improved client compatibility
Fediverse @lemmy.world Hollo 0.7.0: Advanced search, faster notifications, and improved client compatibility
Free and Open Source Software @beehaw.org Histomat of F/OSS: We should reclaim LLMs, not reject them
Open Source @lemmy.ml Histomat of F/OSS: We should reclaim LLMs, not reject them
TypeScript @programming.dev LogTape 2.0.0: Dynamic logging and external configuration
TypeScript @programming.dev Your CLI's completion should know what options you've already typed
General Programming Discussion @lemmy.ml Your CLI's completion should know what options you've already typed
Programming @programming.dev Your CLI's completion should know what options you've already typed
General Programming Discussion @lemmy.ml Hongdown: An opinionated Markdown formatter in Rust
Programming @programming.dev Hongdown: An opinionated Markdown formatter in Rust
Rust @programming.dev Hongdown: An opinionated Markdown formatter in Rust
TypeScript @programming.dev Optique 0.9.0: Async parsers and Git reference validation
TypeScript @programming.dev Designing type-safe sync/async mode support in TypeScript
Node.js @programming.dev Upyo 0.4.0: Modern protocols and email authentication
Fediverse @lemmy.ml Fedify 1.10.0: Observability foundations for the future debug dashboard
Fediverse @lemmy.world Fedify 1.10.0: Observability foundations for the future debug dashboard
Thanks for the feedback! The style choices are intentional and all valid CommonMark:
===/---) for H1/H2 makes major sections visually prominent in plain text, while ATX (###) is used for deeper levels. This hybrid approach optimizes readability in the raw source.The core philosophy is that Markdown should be readable as plain text, not just after rendering. These choices prioritize scanning structure in a text editor. That said, it's definitely an opinionated style—not for everyone!