
  <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, 16 May 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.youngju.dev/tags/tidewave/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-05-16-modern-elixir-phoenix-2026-elixir-1-18-phoenix-1-8-liveview-1-oban-broadway-bumblebee-deep-dive.en</guid>
    <title>Modern Elixir &amp; Phoenix 2026 — A Deep Dive on Elixir 1.18, Phoenix 1.8, LiveView 1.0, Oban, Broadway, Bumblebee, Nx, and Livebook</title>
    <link>https://www.youngju.dev/blog/culture/2026-05-16-modern-elixir-phoenix-2026-elixir-1-18-phoenix-1-8-liveview-1-oban-broadway-bumblebee-deep-dive.en</link>
    <description>Elixir in 2026 is much more than a small functional language. Elixir 1.18 ships a set-theoretic types preview. Phoenix 1.8 lands Scope APIs and ships daisyUI by default. LiveView 1.0 finally went GA. Ecto stabilizes as the canonical DB layer. Oban dominates job processing (with the contentious 999 dollars per year Pro upgrade). Broadway runs Kafka/RabbitMQ/AMQP/SQS data pipelines. Membrane handles audio/video. Igniter does safe code mods. Bumblebee brings Hugging Face Transformers to Elixir. Nx, Axon, and Explorer assemble a BEAM data-science stack. Livebook is the Elixir notebook. Tidewave, unveiled by Jose Valim in September 2025, is Elixir-native LLM serving. The thirty-year-old strengths of BEAM — actors, fault tolerance, soft real-time — explain why Discord, WhatsApp, parts of Toss, BabyDragon in Korea, Drecom and DMM in Japan all picked it. This is the full 2026 stack from VM to GenServer to LiveView to Tidewave in one read.</description>
    <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>elixir</category><category>phoenix</category><category>liveview</category><category>ecto</category><category>oban</category><category>broadway</category><category>membrane</category><category>igniter</category><category>bumblebee</category><category>nx</category><category>axon</category><category>explorer</category><category>livebook</category><category>tidewave</category><category>beam</category><category>erlang</category><category>2026</category><category>deep-dive</category><category>english</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-05-16-modern-elixir-phoenix-2026-elixir-1-18-phoenix-1-8-liveview-1-oban-broadway-bumblebee-deep-dive.ja</guid>
    <title>モダン Elixir &amp; Phoenix 2026 — Elixir 1.18 / Phoenix 1.8 / LiveView 1.0 / Oban / Broadway / Bumblebee / Nx / Livebook 徹底ガイド</title>
    <link>https://www.youngju.dev/blog/culture/2026-05-16-modern-elixir-phoenix-2026-elixir-1-18-phoenix-1-8-liveview-1-oban-broadway-bumblebee-deep-dive.ja</link>
    <description>2026年の Elixir は小さな関数型言語の枠を越えている。Elixir 1.18 の set-theoretic types プレビュー、Phoenix 1.8 の Scope API と daisyUI デフォルト化、LiveView 1.0 の正式リリース、Ecto が築いた DB 抽象の安定、Oban のジョブ処理（と年 999 ドルの Pro 騒動）、Broadway による Kafka/RabbitMQ/AMQP データパイプライン、Membrane の音声/動画処理、Igniter のコード変換、Bumblebee が運ぶ Hugging Face Transformers、Nx・Axon・Explorer で組む BEAM データサイエンス、Livebook ノートブック、そして José Valim が 2025 年 9 月に公開した Tidewave 推論プラットフォーム — 30 年来の BEAM の強み（アクター・耐障害性・ソフトリアルタイム）が、なぜ今あらためて魅力的なのか、なぜ韓国の Toss/BabyDragon、日本のドリコム/DMM/任天堂の一部が Elixir を選ぶのか、まとめて読む。</description>
    <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>elixir</category><category>phoenix</category><category>liveview</category><category>ecto</category><category>oban</category><category>broadway</category><category>membrane</category><category>igniter</category><category>bumblebee</category><category>nx</category><category>axon</category><category>explorer</category><category>livebook</category><category>tidewave</category><category>beam</category><category>erlang</category><category>2026</category><category>deep-dive</category><category>日本語</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-05-16-modern-elixir-phoenix-2026-elixir-1-18-phoenix-1-8-liveview-1-oban-broadway-bumblebee-deep-dive</guid>
    <title>모던 Elixir &amp; Phoenix 2026 — Elixir 1.18 / Phoenix 1.8 / LiveView 1.0 / Oban / Broadway / Bumblebee / Nx / Livebook 심층 가이드</title>
    <link>https://www.youngju.dev/blog/culture/2026-05-16-modern-elixir-phoenix-2026-elixir-1-18-phoenix-1-8-liveview-1-oban-broadway-bumblebee-deep-dive</link>
    <description>2026년의 Elixir는 작은 함수형 언어 그 이상이다. Elixir 1.18의 set-theoretic types 프리뷰, Phoenix 1.8의 Scope API와 daisyUI 기본 적용, LiveView 1.0의 정식 출시, Ecto가 만든 DB 추상의 안정성, Oban의 잡 처리(그리고 Pro $999 논란), Broadway의 Kafka/RabbitMQ/AMQP 데이터 파이프라인, Membrane의 오디오/비디오 처리, Igniter의 코드 변환, Bumblebee가 가져온 HF Transformers, Nx와 Axon과 Explorer로 짜는 BEAM 데이터 사이언스, Livebook 노트북, 그리고 José Valim이 2025년 9월 공개한 Tidewave 추론 플랫폼까지 — BEAM의 액터/내고장성/소프트 리얼타임이라는 30년 묵은 강점이 왜 지금 다시 매력적인지, 그리고 한국의 토스/BabyDragon, 일본의 ドリコム/DMM/任天堂 일부가 왜 Elixir를 골랐는지 한 호흡으로 풀어낸다.</description>
    <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>elixir</category><category>phoenix</category><category>liveview</category><category>ecto</category><category>oban</category><category>broadway</category><category>membrane</category><category>igniter</category><category>bumblebee</category><category>nx</category><category>axon</category><category>explorer</category><category>livebook</category><category>tidewave</category><category>beam</category><category>erlang</category><category>2026</category><category>deep-dive</category>
  </item>

    </channel>
  </rss>
