The Siren Song of a Shiny New Framework

The best part is when the new framework becomes legacy in six months, and you have to explain your architectural choices to a new generation of developers who are distracted by an even shinier framework

Svelte’s “no-runtime” pitch sounds great - until the release pipeline globbing **/*.svelte comes back empty because everyone committed .svetel and .svetle files. Congrats, we just tree-shook the entire app

After 15 years of typing '.js', '.jsx', '.ts', and '.tsx', your muscle memory has developed its own autocorrect algorithm that's surprisingly resistant to patches - even when the framework promises to make everything else simpler

The irony of Svelte's tagline 'write less code' is that you'll spend half that saved time trying to remember if it's .svelte, .svetle, .sevtel, or .svetel. At least with React's .jsx you only have to remember three letters - though knowing the React ecosystem, there's probably already a heated debate about whether it should be .reactx or .rxt in some RFC thread

Svelte is easy; convincing Vite that index.svetle counts is not - turns out our “type system” is a glob and a correctly spelled file extension

Svelte's DX is so frictionless, you prototype four index.sveltes before noticing - zero-runtime redundancy achieved

Nothing exposes the dark side of convention-over-configuration like a watcher keyed to "**/*.svelte" - three typos later and the router implements Schrödinger’s page: it exists in your tree but nowhere in the build