3 ms·
Perhaps it's because what makes a codebase messy is having written code in it over time. In the beginning, those Node.JS codebases were clean and manageable. T
by curun1r 11y ago
Perhaps it's because what makes a codebase messy is having written code in it over time.
In the beginning, those Node.JS codebases were clean and manageable. Then came bug fixes, changing requirements and refactors. 2 years worth of that led to something that was quickly becoming unmanageable.
But then came Go and, after a rewrite, everything was clean again! It doesn't matter than the code base is only 3 months old, I'm sure it's going to stay this clean forever!
But hey, should those Go codebases become messy a couple of years from now, I'm sure Rust will have matured into a worthy successor and, after a rewrite, we'll all have the cleanest codebases ever!
- spion 11y agoSimilar path here, but we cleaned things up using TypeScript. Its incredible how much easier things get when you need to refactor if you have types.