Following
Public ActivityPub posts from actors connected with @me@changkyun.kim.
#LogTape 2.2.0 is out! The headline is two new packages: @logtape/lint adds lint rules for ESLint v8/v9 (flat config), Oxlint, and Deno Lint that catch common logging mistakes before they reach production: template literal interpolation in message arguments, eager property evaluation where lazy is needed, unawaited async log callbacks, and missing meta sink configuration. @logtape/testing gives you createLogRecorder() and domain-aware assertion helpers, replacing the hand-rolled array-sink boilerplate that every project ends up writing. Other highlights: context: true on Express/Hono/Koa/Elysia middleware handles request ID generation, x-request-id header propagation, and implicit context. One option instead of several moving parts. Seven performance optimizations on the enabled-logging hot path New logtape.org website Full release notes: https://github.com/dahlia/logtape/discussions/179 #JavaScript #TypeScript #Deno #Node #NodeJS #Bun #logging #opensource
洪 民憙の質問箱で質問を受け付けています！気軽に送ってください！🙏 https://fediqb.y-zu.org/questionbox/@hongminhee@hollo.social #FediQB
洪民憙(홍민희)의 質問函(질문함)에서 質問(질문)을 받고 있습니다! 便(편)하게 보내주세요! 🙏 https://fediqb.y-zu.org/questionbox/@hongminhee@hollo.social #FediQB
오늘 바조콘 2026에서 發表(발표)한 〈Gukhanmun: 國漢文(국한문)을 한글로 바꾸기〉 슬라이드 資料(자료)를 共有(공유)합니다. 오늘 들어주신 모든 분들께 感謝(감사)드립니다. https://hongminhee.codeberg.page/gukhanmun-bazocon-2026/
@cheeaun Yeah, I personally prefer the compact syntax (which is widely used) over “readable” ones, but if people get hard to read them, “readable” ones can be a good alternative.
@cheeaun Yeah, exactly! I guess your ex-colleagues might be bothered if patterns were written in Parsec-style syntax. 🤔
The reason people avoid regular expressions is ultimately because of the syntax. No indentation, no comments. It might be a minority opinion, but I think the x (EXTENDED) flag should be the default for regex.
@smallcircles Thanks for the kind words! Stay tuned!
Fedify Studio finally has a proper name: DrFed. We just got @nlnet funding too. RE: https://hackers.pub/@drfed/019ed3c9-7e8c-782f-a512-5fbc75a4610b
Hackers' Pubにも数日前に韓国語で書いたことですが、元々Smalltalkに大きな幻想を抱いていて、Lispを最高のプログラミング言語だと信じていました。食べていくためにPythonを使っていましたが、基本的には「許容できるLisp」（acceptable Lisp）として扱っていたのです。 それがどういうわけか、Haskellを本格的に使い始め、それ以来、静的型検査ができないプログラミング言語には魅力を感じなくなりました。Pythonはあっという間に道具箱から姿を消し、その座をTypeScriptが代わりました。Smalltalkへの幻想ももうありません。 一言で言えば、Haskellがプログラミング言語の好みを180度変えてしまったというわけです。 RE: https://post.syobon.net/objects/ee270cf1-4555-4b63-b898-49fb38724426
「中華LLM」という表現、すごく面白い。🤣 あ、急に冷やし中華が食べたくなった。😅 RE: https://mstdn.y-zu.org/@Yohei_Zuho/116757411712201439
Optique 1.1.0 is out. The headline is the new @optique/discover package: point it at a directory of #TypeScript files and it builds a full #CLI command tree, with typed handlers and help/completion included automatically. Also new: value parsers for file sizes, CSS colors, semver strings, JSON, and KEY=VALUE pairs; seq() for ordered positional grammars; negatableFlag() for --color/--no-color patterns; async Zod/Valibot helpers. https://github.com/dahlia/optique/discussions/834
國漢文(국한문)을 한글로 바꿔주는 소프트웨어인 Gukhanmun 0.2.0이 릴리스되었습니다. 《標準國語大辭典(표준국어대사전)》과 더불어 《우리말샘》 데이터를 包含(포함)하게 되었고, 各種(각종) 코너 케이스를 더 잘 다루게 되었습니다. 또한, 國漢文(국한문) 原文(원문)에 括弧(괄호)로 한글 倂記(병기)가 되어 있을 境遇(경우), 이를 結果文(결과문)에서도 反映(반영)하여 漢字(한자) 倂記(병기)가 되거나 한글 讀音(독음)이 달리게 되었습니다. 그 밖에도 여러 改善(개선) 事項(사항)들이 있으니, 仔細(자세)한 內容(내용)은 릴리스 노트를 參考(참고)하시기 바랍니다. https://github.com/dahlia/gukhanmun/discussions/10
I write my name in Chinese characters: 洪民憙. In English I still include them, writing Hong Minhee (洪民憙) rather than the romanization alone. Part of it is meaning: Chinese characters carry it, hangul doesn't. Mostly, though, it's about the direction of loss. You can derive a Korean or romanized reading from 洪民憙; you can't go the other way. Given 홍민희 or Hong Minhee alone, there's no recovering which characters were intended. I don't much mind how my name gets pronounced. If a Chinese speaker reads it as Hóng Mǐnxī, or a Japanese speaker arrives at something different, that's fine. The characters are the same. Classical Chinese once worked this way across East Asia: one written text, many readings. What I care about is the notation.
This is like magic, absolutely awesome. I'm really looking forward to PostgreSQL 19. RE: https://mastodon.social/@lobsters/116738654866957041