"Why craft-lovers are losing their craft" by Hong Minhee (@hongminhee.org) writings.hongminhee.org/2026/03/craf...

We make our choices, and then our choices make us. https://writings.hongminhee.org/2026/01/ethics-of-small-actions/

좋은 글.. writings.hongminhee.org/2026/03/craf... Marx는 자본론에서 영국의 러다이트 운동을 이렇게 평했다. 노동자들이 기계 자체와 기계의 자본주의적 적용을 구분하고, 따라서 물질적 생산 수단 그 자체가 아니라 그것의 사회적 착취 형태를 공격하는 법을 배우기까지는 시간과 경험이 필요했다. 방직기를 부순 노동자들의 분노는 정당했다. 방향이 잘못됐을 뿐이다. 베틀이 노동 시간을 늘린 게 아니었다. 자본이 그랬다. 베틀이 노동자를 기계의 부속물로 만든 게 아니었다. 자본이 그랬다.

This Marxist lens on the different ways my peers and network is reacting to GenAI was more interesting than I expected https://writings.hongminhee.org/2026/03/craft-alienation-llm/

Why craft-lovers are losing their craft https://lobste.rs/s/vxsjiv ##vibecoding

LLM coding tools didn't split developers into craft-lovers and make-it-go people. They revealed a split that was always there. The grief craft-lovers feel isn't about the tools. It's about the market penalizing them for it.

Personal update: I resigned from Deno two weeks ago. Yesterday was my last day at Deno. Working on Deno, Deno Deploy, JSR, and Fresh with my world class colleagues has been an absolute honor. I wish everyone who I have worked with at Deno the absolute best - continue building groundbreaking things!

합법이면 공정한가: AI 재구현과 카피레프트의 침식 — 洪民憙雜記 writings.hongminhee.org/2026/03/lega...

https://writings.hongminhee.org/2026/03/legal-vs-legitimate/ > The norms that open source communities built over decades did not wait for court approval. People chose the GPL when the law offered them no guarantee of its enforcement, because it expressed the values of the communities they […]

writings.hongminhee.org/2026/03/lega... #lgpl #foss #ai

🌐合法性と正当性は同じか：AIの再実装とコピーレフトの侵食 https://writings.hongminhee.org/2026/03/legal-vs-legitimate/ via #HackerNews

"Whatever courts eventually decide about AI reimplementation, the question we need to answer first is not a legal one. It is a social one. Do those who take from the commons owe something back?" #OSS #copyleft #license #software #GenAI writings.hongminhee.org/2026/03/lega...

Interesting arguments arise when an existing project is copied via supplying the existing test cases to the GenAI LLM tools to re-implement the software (and then release under a different license) writings.hongminhee.org/2026/03/lega...

Salvatore Sanfilippo (antirez) and Armin Ronacher (mitsuhiko) both argue that AI reimplementation of copyleft libraries is fine. Their legal reasoning might be correct. That's not the point. Legal and legitimate are different things—and both pieces quietly assume otherwise.

github.com/dahlia/fedif... Fedify ってめっちゃ良さそう！こういうのがあると、ActivityPub の自分のためのサーバーをもっと拘って作れるようになるからめっちゃワクワク！

#Optique 1.0.0 preview: runWithConfig() is gone—run() now accepts source contexts. Meta command config gets independent command/option sub-configs. bindConfig() gains config-file metadata for path resolution. #TypeScript #CLI

The really cool thing about this new architecture is that it can enable Client to Server architecture for AP with fedify (maybe vocab packages could be used in the browser too!)

Fedify 2.0.0—the biggest release yet! • Modular package architecture • Real-time debug dashboard • ActivityPub relay support • Ordered message delivery • Permanent failure handling Breaking changes included—see the migration guide before upgrading. Full release notes are on GitHub.

fedi.blue 라는 도메인을 샀는데 뭔가 아이디어가 안 떠오르네요... 블스랑 연합우주 모두에서 사용 가능한 앱이었으면 좋겠는데... 혹시 아이디어가 있으신 분은 편하게 말씀해주시면 감사하겠습니당 알티도 감사해요!

Interesting to see combinator conditions on #typescript for CLI. This is something that's hard to do in any CLI library. Easier with typed languages, but still can be complex. Very cool to see with #optique and their approach leveraging the type system. 😎

Optique 0.10.0 is out—the largest release yet for this type-safe TypeScript CLI parser. Highlights: runtime context system, config file integration, man page generation, inter-option dependencies, 11 network value parsers. Last pre-release before 1.0.0.

We have the pleasure of having @hongminhee.org who will give a presentation about @fedify.hollo.social.ap.brid.gy "an opinionated #ActivityPub framework for TypeScript that handles the protocol plumbing" It is an open free event and everyone is welcome!

Hot take: We shouldn't block AI companies from training on our F/OSS code. We should require them to free the models they train. That's not naïve idealism—it's the same strategy that built GNU/Linux. Why training copyleft might be our GPL moment:

LogTape 2.0.0 released! A zero-dependency logging library for JavaScript/TypeScript. New in 2.0: lazy() for dynamic context values, config from JSON/YAML files, direct Error logging, async lazy evaluation, time-based log rotation, Elysia integration, and more.

Why I do open source

Hongdown 0.2.0 released! Hongdown is an opinionated Markdown formatter written in Rust, now available as a WebAssembly library for Node.js, Bun, Deno, and browsers. New: smart sentence case for headings, SmartyPants-style typography, external code formatters, and directory batch formatting.

if people no longer read the code, API is no longer targeting humans, is there still a need for "good API design"? is it still worth the effort to figure out what would be the best for users, instead of the best of ai to understand/use? I don't know.

When building CLI tools, shell completion usually treats each option in isolation. But sometimes valid values for one option depend on another—like branch names depending on which repository you're targeting. Wrote about how I solved this in Optique, a type-safe CLI parser for TypeScript.

Une lib de logging pour JavaScript qui ambitionne d'ajouter du logging facilement à vos packages. Ensuite, libre à l'utilisateur de votre package de décider s'il veut activer le logging ou pas. Ça me fait un peu penser à log4j pour Java 🤔 🔗 https://logtape.org/ #JavaScript #lib #log

How do you make one CLI option's value affect another's validation and completion? Like `git -C <path> branch <TAB>` completing branches from that path. I think I've found a nice solution for Optique: topologically sort dependencies between value parsers.

New from me: X is A Power Problem, Not a Platform Problem https://connectedplaces.online/reports/a-power-problem-not-a-platform-problem/

Sentry just dropped a blog post on “Trace-connected structured logging with LogTape.” It's incredibly rewarding to see the library getting this kind of recognition from the industry leaders in observability. A huge milestone for the project.

I finally gave in and wrote my own markdownlint rules to enforce my peculiar and stubborn Markdown style. Probably no one else will ever need these, but I've published them as open source anyway.

Wrote a tutorial on building CLI apps with Optique, a TypeScript CLI parser I've been working on. If you've ever wanted discriminated unions from your argument parser, this might interest you.

Optique 0.9.0 released! Two big features: • Async parsers: validate against databases, APIs, or filesystems with full type safety • New @optique/git package: validate branch names, tags, and commits against real Git repos All backward compatible. Existing code works unchanged.

今日のZennトレンド 2026年版：JavaScript/TypeScriptのロギング入門 この記事は、JavaScript/TypeScriptにおける効果的なロギング方法を解説しています。 console.logの限界を指摘し、軽量で多機能なロギングライブラリLogTapeの導入を提案。 ログレベル、カテゴリ、シンク、構造化ログといったロギングの基本概念を説明し、LogTapeを用いた具体的な設定方法や活用例を紹介しています。 本番環境での障害対応や効率的なデバッグに役立つロギング環境構築のヒントが得られます。

https://zenn.dev/hongminhee/articles/e0d19ae2c4e042 本番環境での障害時に役立つログ構築について解説します。 console.logの限界を整理し、実用的なロギング環境の構築方法を紹介します。 LogTapeという依存ゼロで軽量なロギングライブラリを使用します。

Wrote about designing type-safe sync/async mode support in TypeScript. Making object({ sync: syncParser, async: asyncParser }) automatically infer as async turned out to be trickier than expected.

I wrote about setting up logging that's more useful than console.log() but doesn't require a Ph.D. in configuration. Covers categories, structured logging, request tracing, and production tips.

Just released Vertana 0.1.0—an LLM-powered translation library for TypeScript/JavaScript that uses agentic workflows to gather context for higher-quality translations.

I'm proposing a new way to configure LogTape from plain objects (JSON/YAML/TOML), similar to Python's logging.config.dictConfig(). This would make it easier to manage environment-specific configs without code changes. Thoughts?

Upyo 0.4.0 is out. Upyo is a cross-runtime email library for JavaScript. This release adds JMAP transport, DKIM signing for SMTP, and message-level idempotency keys.

내 트리를 꾸며줘!

Designing a dual-mode sync/async API in TypeScript is tricky. For Optique (CLI parser), I want to add async support while keeping the existing sync API intact. Exploring type-level mode propagation so combinators automatically become async when any child is async.

Someone said my F/OSS docs are confusing, then “maybe that's fine if focused on your Chinese community.” I'm Korean. Everything's in English. This is what non-white maintainers deal with.

A linter for deno.json that enforces Deno best practices. Created by @uki00a.bsky.social. github.com/uki00a/deno-...

Still stick with Pino? Give LogTape a try!

LogTape 1.3.0 released! This version adds first-class integrations for Express, Fastify, Hono, Koa, and Drizzle ORM—plus a new withCategoryPrefix() for SDK authors who want cleaner log hierarchies.

なるほど、logtape って npm の "debug" package を置き換えるようなタイプのライブラリだったのか zenn.dev/hongminhee/a...

I couldn't find a logging library that worked for my library, so I made one. Here's how LogTape powers Fedify's logging—and why library authors might want a different approach than winston or Pino.