> that will be hobbled because of those early decisions for a long, long time. Perhaps this is why a programmer would want to rewrite a system & tout "funny su

> that will be hobbled because of those early decisions for a long, long time. Perhaps this is why a programmer would want to rewrite a system & tout "funny success stories" about the effort & results? https://news.ycombinator.com/item?id=25844428 https://news.ycombinator.com/item?id=25844428 > Why couldn't you just upgrade the dependencies once then set up the same CI/CD you're presumably using for Svelte so that you can them upgrade versions easily? Because the existing system was painful & time/energy intensive to upgrade. It happens with tight coupling, dependency hell, unchecked incidental complexity, architecture churn, leaky abstractions, etc... Maintenance hell & > 1 month major version upgrades tend to occur with large, encompassing, first-mover frameworks, often built on a brittle set of abstractions, as they "mature" & "adapt" to the competition. e.g. Rails, Angular...