Robin, thanks for the fiery take—love the skepticism, even if it’s got a “REST in peace”

Why’s URI versioning like /v1/products so common?

quick, easy, and log-friendly. But common doesn’t mean RESTful—Fielding’s 2008 post “REST APIs must be hypertext-driven” buries it as RPC’s ghost, coupling clients to brittle paths. Your “personal opinion” jab stings, but this isn’t just me—Stripe’s Stripe-Version and GitHub’s Accept: vnd.github.v3+json prove headers scale without URI graves. Best practice? Not yet , but it’s got REST’s grim reaper nodding.

Maintenance-wise, my if/else block’s a creaky skeleton, But it beats URI versioning’s zombie horde of duplicate controllers (V1, V2, V3…) you can’t kill when old apps cling to /v1. One endpoint, one path, less rot.

I get the “don’t do this” chills—headers feel like a coffin for URI comfort. But this isn’t quirky me; it’s REST’s spirit haunting bad design. You’re keeping me sharp, and I dig that! Stick to URI tombstones or got a darker fix?