YuukiJyoudai

4 ms·

1. 1.▲
   by YuukiJyoudai 2mo ago

   Well written. I completely agree with you.
2. 2.▲
   by YuukiJyoudai 7mo ago

   The Matrix got me into programming, so honestly this was inevitable.
3. 3.▲
   by YuukiJyoudai 7mo ago

   Agreed. IDs feel like the right starting point — names before verbs. From there, I could imagine thin protocol layers emerging above — renderers, voice interfaces, AI agents each binding their own behavior to the same IDs. Markdown stays pl
4. 4.▲
   Ask HN: How will distribution work when AI makes creation nearly free?

   1 points by YuukiJyoudai 7mo ago|1 comments
5. 5.▲
   Ask HN: What Comes After Markdown?

   10 points by YuukiJyoudai 7mo ago|13 comments
6. 6.▲
   by YuukiJyoudai 7mo ago

   Thanks for the reply — first time posting on HN, so this really means a lot. Just checked out Voiden. Same philosophy, different layer: plain text, git-native, composable. You made API requests executable Markdown. We made dev workflows exe
7. 7.▲
   by YuukiJyoudai 7mo ago

   Thanks for being my very first HN reply — genuinely appreciate it. The short answer: I cheated by staying in the Apple ecosystem. The sync has two layers: - *macOS ↔ iOS*: iCloud handles it natively. Obsidian's iCloud vault is just a f
8. 8.▲
   Show HN: Cc-md – Zero-cost Obsidian sync across iPhone, Mac, and GitHub(github.com)

   8 points by YuukiJyoudai 7mo ago|4 comments