Episode Details

This week Kamran and Erik discuss when ORMs are helpful... or hurtful. They cover trade-offs, the spectrum of abstraction, the value of escape hatches, and the options available to you in the TypeScript ecosystem.

Week of February 17, 2025

• (05:54) - News: Ember 6.2 Released
• (07:16) - News: Deno 2.2 Released
  • npm-check-updates package
  • Package JSON Upgrade VS Code extension
  • https://github.com/vuki656/package-info.nvim for Neovim

Community Highlights

• (16:48) - Community Highlights: UseTypeScript for Your Stored Procedures?!
• (17:20) - Community Highlights: Node API Compatibility Across Runtimes
• (17:58) - Community Highlight: Why Type Catalogs Can Be Better Than Unions
• (19:05) - Community Highlight: tapi.js Automatically Maps JSON to Strongly-Typed Classes
• (20:33) - Community Highlight: Standard Schema Hopes to Align TS Validator Libraries
• (21:34) - Community Highlight: 2ality: Read-only accessibility in TypeScript

 Deep Dive: TypeScript ORMs

• (22:56) - Deep Dive: TypeScript ORMs
• (24:21) - Deep Dive: Code-first or Database-first?
• (25:42) - Deep Dive: What Pain Do ORMs Solve?
• (27:21) - Deep Dive: When Should You Use an ORM?
  • Martin Fowler's ORM Hate article
  • Primeagen's Don't Use an ORM reaction video
• (30:02) - Deep Dive: To Use An ORM Or Not to Use an ORM?
• (31:47) - Deep Dive: SQL Builders vs. Abstracted ORMs
• (32:28) - Deep Dive: Do You Have An Escape Hatch?
• (33:36) - Deep Dive: Are ORMs A Symptom of Poor Data Architecture?
• (37:01) - Deep Dive: TypeScript ORM Landscape
• (37:26) - Deep Dive: Drizzle ORM
  • Fireship's Drizzle in 100 seconds
  • Works with

    Listen Now