Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

So, um, the phrase "legally forced" really does not go with "happened easily".

Ignoring what "legally" forced entails, and just focusing on the mechanics of renaming stuff: Even if your code base can be updated with a simple "s/old/new/" regex (and, IME, this never, ever works as well as you thought it would, and always creates a long tail of manual grepping and editing), you still have to fix the docs, deal with breaking API changes, support multiple versions, provide upgrade paths, deal with confused users, etc. etc. etc.

And, um, confusingly, the examples you cite are actually even more complicated and work-intensive than what is being talked about in this article, because they also require URL / domain name updates, legal document changes, regulatory filings, etc. etc.

TLDR: the contention that "name changes happen easily" is not an accurate description of the situations you are citing.



Can confirm. Renaming Ethereal to Wireshark involved a bunch of code and documentation updates, registering word and design trademarks across jurisdictions, and in our case we didn't have control over the old domain, so I had to contact a bunch of people linking to ethereal.com and ask them to link to wireshark.org instead. I don't know if the last part would even be possible today.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: