Rename or contribute back? MACS3 optimizers debate the ethics of releasing sped-up open-source code
jmschreiber91 · x · 2026-10-12
An open-source etiquette debate: Nezar suggested optimizing someone's code and pushing back upstream for merge. jmschreiber91 (who optimized MACS3) argued that taking another group's algorithm, optimizing it, and releasing it under a new name as your own is wrong — even a 'macs3-lite' rename without contacting maintainers encourages bad behavior. His takeaway: at least talk to the original authors about the best path, to avoid a fragmented ecosystem of unmaintained rewrites. nskene added that anyone who just speeds up someone's code and releases it themselves should be shunned.
Related event: Debate Erupts Over Ethics of Republishing AI-Accelerated Code(3 posts)→
More from Fun
- 'PHP is one trillion lines of terrifying C': security veterans mock the fix-one-vuln mindset — dyn___ · 2026-10-23
- Opus 5.5 generates sci-fi movie titles entirely in code—no assets, no samples — prasenx · 2026-10-23
- Dev runs 5 Claude Code sessions that coordinate via MCP Agent Mail to root his network cameras — doodlestein · 2026-10-23
- The classic tech joke: 'My servers were NOT impacted by the RCE from the PHP tech debt' — MickeySteamboat · 2026-10-23
- Delivery robot spotted cruising city sidewalks on its own — HomeNowWTF · 2026-10-23
- CTO exits blood-testing startup of Elizabeth Holmes' partner, dubbed "Theranos 2.0" — annatonger · 2026-10-23