
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Chaos and Order</title>
      <link>https://www.youngju.dev/blog</link>
      <description>천천히 올바르게. AI Researcher &amp; DevOps Engineer Youngju&#39;s tech blog. GPU/CUDA, LLM, MLOps, Kubernetes AI workloads, distributed training, and data engineering.</description>
      <language>ko</language>
      <managingEditor>fjvbn2003@gmail.com (Youngju Kim)</managingEditor>
      <webMaster>fjvbn2003@gmail.com (Youngju Kim)</webMaster>
      <lastBuildDate>Sat, 11 Jul 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.youngju.dev/tags/compile-times/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.youngju.dev/blog/2026-07-11-scarf-leaves-haskell.en</guid>
    <title>Why Scarf Reluctantly Left Haskell After 7 Years — The Real Cost of a Language Choice</title>
    <link>https://www.youngju.dev/blog/2026-07-11-scarf-leaves-haskell.en</link>
    <description>Scarf is moving its backend off Haskell to Python after seven years in production. The interesting part is why. Founder Avi Press readily admits Haskell kept most of its promises — reliability, type safety, performance — yet points to compile times and ecosystem friction as the deciding costs. In a workflow where several AI agents explore branches in parallel, cold-build waits shifted from a papercut to the dominant cost of a unit of work. This post looks at what really makes a team leave a language it still respects, and why language fit is relative to the era and the way you build.</description>
    <pubDate>Sat, 11 Jul 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>haskell</category><category>python</category><category>engineering-decisions</category><category>compile-times</category><category>ai-assisted-development</category><category>migration</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/2026-07-11-scarf-leaves-haskell.ja</guid>
    <title>Scarfはなぜ7年使ったHaskellを惜しみつつ手放したのか — 言語選択の本当のコスト</title>
    <link>https://www.youngju.dev/blog/2026-07-11-scarf-leaves-haskell.ja</link>
    <description>Scarfは7年間プロダクションで動かしてきたHaskellを、Pythonへ移行しつつあります。興味深いのはその理由です。創業者のAvi Pressは、Haskellが信頼性・型安全性・性能という約束の多くを守ったと率直に認めたうえで、決め手になったのはコンパイル時間とエコシステムの摩擦だったと述べます。複数のAIエージェントがブランチを並行して探索する開発スタイルでは、コールドビルドの待ち時間がささいな不便から最大のコストへと変わったというのです。本稿は、まだ敬意を抱く言語をチームが手放す本当の理由と、言語の適合性が時代と作り方によって変わるという教訓を整理します。</description>
    <pubDate>Sat, 11 Jul 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>haskell</category><category>python</category><category>engineering-decisions</category><category>compile-times</category><category>ai-assisted-development</category><category>migration</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/2026-07-11-scarf-leaves-haskell</guid>
    <title>Scarf는 왜 7년 쓴 하스켈을 아쉬워하며 떠났나 — 언어 선택의 진짜 비용</title>
    <link>https://www.youngju.dev/blog/2026-07-11-scarf-leaves-haskell</link>
    <description>Scarf는 7년간 프로덕션에서 돌리던 하스켈을 파이썬으로 옮기고 있습니다. 흥미로운 건 그 이유입니다. 창업자 Avi Press는 하스켈이 신뢰성·타입 안전성·성능이라는 약속을 대부분 지켰다고 인정하면서도, 결정적 비용은 컴파일 시간과 에코시스템 마찰이었다고 말합니다. 여러 AI 에이전트가 브랜치를 병렬로 탐색하는 개발 방식에서, 콜드 빌드 대기 시간이 사소한 불편에서 가장 큰 비용으로 바뀌었다는 것입니다. 이 글은 아직 존중하는 언어를 팀이 떠나게 만드는 진짜 비용과, 언어의 적합성이 시대와 작업 방식에 따라 달라진다는 교훈을 정리합니다.</description>
    <pubDate>Sat, 11 Jul 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>haskell</category><category>python</category><category>engineering-decisions</category><category>compile-times</category><category>ai-assisted-development</category><category>migration</category>
  </item>

    </channel>
  </rss>
