1. Project‑file stability is a deal‑breaker
“I once tried learning how to RE with radare2 but got very frustrated by frequent project file corruption … I never actually got further.” – aktau
“I got corruption a lot, like every 4‑5 saves … I was just agit reset --hardaway from restoring a good state.” – alberto‑m
2. Ghidra vs. IDA (and Binary Ninja) – cost, usability, and feature set
“IDA is far far better at interrupting tasks/crash recovery … Ghidra just leaves you with nothing.” – apple1417
“IDA is the better tool if you're being paid to work with architectures that IDA supports well … Ghidra is the better tool if you're dealing with exotic architectures.” – q3k
“Binary Ninja deserves a mention … I much prefer Binary Ninja for the task of building up an understanding of large binaries.” – alexrp
3. NSA’s open‑source release and the “backdoor” debate
“It’s a NSA open‑source reverse‑engineering framework … the public face of Ghidra works at Praxis.” – bri3d
“There’s no NSA backdoor in Ghidra … it’s just a program that will often be running on disconnected systems.” – dizzy9
4. AI/MCP integration is reshaping RE workflows
“The gains come from pairing Ghidra with a coding agent. It works amazing well.” – cactusplant7374
“There is MCP for Ghidra … I highly recommend it.” – quux0r
“AI is not that terrible at using Ghidra … we released a benchmark on that.” – jakozaur
These four threads capture the discussion’s core concerns: reliability of project files, comparative strengths of the major tools, the implications of NSA‑originated open‑source software, and the emerging role of AI‑powered assistants in reverse engineering.