7 ms·
I’ve seen people do this and I’m always confused, do they believe they will never have to reason about the code ever again. I suppose if it is like the Zig Rew
by sashank_1509 2mo ago
I’ve seen people do this and I’m always confused, do they believe they will never have to reason about the code ever again.
I suppose if it is like the Zig Rewrite where essentially all development is being done by Claude, I can imagine this making sense.
But in any other case, you had a codebase that presumably you wrote, you could reason about, you could refactor etc. and then you made it into a completely unintelligible code base, which even if written cleanly will take a long time to reason about. Typescript to Rust is not just syntax changes. It doesn’t make sense to me, unless you believe you will be completely out of the loop in managing this code in the future.
- jemmyw 2mo agoA small typescript util rewritten into rust is going to look so similar that I don't think this will be a problem. As the parent commenter said, maybe not for a larger project. But rust semantics are really close to typescript for the most part, at least the bits you'd use for a simple tool.
- BluSyn 2mo agoThis wasn't a codebase I originally wrote or cared to reason about deeply. It's fairly straight-forward rust, so not hard to understand or follow. Again, this was originally just a test to see how well it would work (better than I expected). Not something I need to maintain much going forward, so I have no reason to manage the code manually ever.