I think the urge to seastead comes from the same place as the urge to refactor code. "Let's just start over, it's bound to be way better because of all we've learned." But as well know, there is no guarantee that refactoring from scratch is going to produce a better product.
Modern states are like old codebases. They are a huge pain in the ass to maintain, BUT they also contain bug fixes and tweaks from 1,000+ solved problems. In fact all those fixes are probably why it is such a pain in the ass to maintain. That doesn't mean they aren't good fixes that are still relevant and necessary.
Uh, what you describe is rewriting, not refactoring... Refactoring is often a great investment, and is not done 'from scratch'.
I would question your assertion that modern states have 1,000+ solved problems. They have no unit testing, shoddy QA if any, etc. It's a bad analogy, imho. When they do generate a 'tweak' it is often not solving a problem, but generating more problems than it solves.
Comments
I think the urge to seastead comes from the same place as the urge to refactor code. "Let's just start over, it's bound to be way better because of all we've learned." But as well know, there is no guarantee that refactoring from scratch is going to produce a better product.
Modern states are like old codebases. They are a huge pain in the ass to maintain, BUT they also contain bug fixes and tweaks from 1,000+ solved problems. In fact all those fixes are probably why it is such a pain in the ass to maintain. That doesn't mean they aren't good fixes that are still relevant and necessary.
Uh, what you describe is rewriting, not refactoring... Refactoring is often a great investment, and is not done 'from scratch'.
I would question your assertion that modern states have 1,000+ solved problems. They have no unit testing, shoddy QA if any, etc. It's a bad analogy, imho. When they do generate a 'tweak' it is often not solving a problem, but generating more problems than it solves.