Commenters debated REA as a powerful, open-source step toward automating reverse engineering. Some praised the project and planned integrations (MiroslavPokorny, areoform), noted neat demos like recreating games (nailer) and clones of commercial apps appearing in feeds (nirav72), and joked about an evolution of installation ergonomics via curl|bash (mb7733). Others highlighted practical benefits: running locally, packaging for less experienced users (Neywiny, areoform), and potential for AI-assisted binary analysis to improve security scanning and sandboxing (carsoon). Enthusiasts also predicted legal fights over closed-source targets (rvz) and celebrated contributors (epsteingpt).
Several commenters questioned whether REA materially improves existing reverse-engineering workflows. Ethan, cedws, tptacek and djmips said seasoned practitioners prefer Ghidra, radare2 or Claude-driven pipelines and saw REA as more for novices or those who like GUIs. Critics warned about safety, legal and talent-pipeline downsides: areoform argued that model guardrails, DMCA-like restrictions and corporate lobbying could lock away knowledge and harm upskilling, and pointed to Opus/Anthropic access changes (LoganDark) as examples. Others stressed installer security tradeoffs between dynamic installers and vettable packages (t-writescode), leaving opinion split between enthusiasm for democratization and concern about usefulness, legality and long-term control.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.