Add podcast episode 63: oxlint vs ESLint performance comparison

[AnnatarHe]

Summary

Added a new podcast episode (EP63) discussing oxlint as a faster alternative to ESLint, featuring performance comparisons and migration guidance.

Changes

• Created new podcast episode metadata and show notes for EP63
• Episode covers oxlint performance improvements (50-100x faster than ESLint in real-world testing)
• Includes comparison with Biome and discussion of plugin system compatibility
• Provides practical migration guidance for existing projects
• Links to episode on Xiaoyuzhoufm, YouTube, and Bilibili platforms

Details

The episode content focuses on:

• Real-world performance benchmarks (ESLint: 1m43s vs oxlint: 21s)
• Plugin system comparison and JavaScript rule writing capabilities
• Impact of linting speed on AI-assisted development workflows
• Migration recommendations for different project sizes

https://claude.ai/code/session_01Fv2TbuX8ehghr8gcnsMibP

[claude]

Code Review: EP63 — oxlint vs ESLint

Overview

This PR adds a new podcast episode MDX file (ep63.mdx) covering oxlint as a faster alternative to ESLint. It is a pure content addition with no code changes.

---

✅ What's done well

• Follows project conventions exactly: frontmatter structure, field ordering, slug pattern (/posts/ep63), season/episode numbering, and biliUrl format all match ep62.mdx and other recent episodes.
• Publication date (2026-05-05 14:00:00) aligns with the episode release date.
• Show notes quality: well-structured Chinese content with clear bullet points, appropriate emoji use, a call-to-action, and BGM attribution — consistent with the podcast's style.
• Categories are specific and relevant (oxlint, eslint, tooling, frontend, javascript, typescript).

---

⚠️ Minor observations

• size: 0 and duration: 0: These are zero-valued, which is the same as ep62.mdx and apparently accepted for this project. However, the CLAUDE.md notes that "all required frontmatter fields are properly filled to maintain RSS feed compatibility". Podcast RSS standards (e.g. <enclosure length>) expect accurate file size and duration — many podcast clients and directories (Apple Podcasts, etc.) may display 0:00 duration or behave unexpectedly. Worth filling in once the audio is finalized, even if it's done in a follow-up commit.

• excerpt and subtitle duplicate title: This is consistent with other episodes, so no action needed — just a note that adding distinct descriptions here could improve SEO and podcast directory listings over time.

• guid: 63 — uses a bare integer. This is consistent with existing episodes, so no issue for this PR. (A full URL-based GUID is recommended by the RSS spec but changing the pattern is out of scope here.)

---

🚫 No concerns on

• Security: Pure static content, no user input or dynamic code.
• Performance: No impact on build performance for a single MDX file.
• Test coverage: Per CLAUDE.md, this project has no automated tests; manual verification is sufficient.

---

Verdict

Looks good to merge. The content is well-written and the file follows all established conventions. The only actionable item is updating size and duration once the final audio file is available — this can be a quick follow-up commit after publishing.