- I’ve seen a lot of debate here comparing Go’s issues (like nil handling or error scoping) to Rust’s strengths.
- As someone who’s worked with C/C++ and Fortran, I think all these languages have their own challenges—Go’s simplicity trades off against Rust’s safety guarantees, for example.
- Could someone share a real-world example where Go’s design caused a production issue that Rust or another language would’ve avoided?
- I’m curious how these trade-offs play out in practice.
Sorry, I don't do Go/Rust coding, still on C/C++/Fotran.
Tools like aider or cursor composer does not help for complex code as they destroy your mental code model of the solution you working on.
This tools help a bit for initial mocks, but even that, I don't like as they create code that I don't know and I need to review it all to know where things is.
When you are doing complex software, you need to build a good mental code model to know where things is, especialy when you need to start to debug issues, not knowing where things is is a mess and very annoying.
This days, I almost don't use this tools anymore, I just prefer basic line auto-completion.
Possible, but only if you do it in "Founder Mode", i.e., no distraction, code a MVP and that's it.
Even if you get distracted with IA our premature optimization, you rekt.
In fact, you have 1 week to build the MVP, after that, all your team or you is burned out.
It's like you hiding shorts on youtube.