Don’t Call Your Open Source Project Something Vulgar

The following definitions of vulgar apply (see Merriam-Webster):

  1. Lacking in cultivation, perception, or taste
  2. Morally crude, undeveloped, or unregenerate
  3. Offensive in language
  4. Lewdly or profanely indecent

Vulgar names have three downsides:

  1. Vulgarity is inherently bad, i.e. it is better to be less vulgar.
  2. Vulgar names generally disturb other people. The name may thus reflect badly on the user of the software.
    • For example, a work colleague may think you’re weird if they see the “Doom Emacs” editor on your screen.
  3. Again, vulgar names generally disturb other people. The name may thus limit the spread of the project, which goes against the principles of open source.
    • More specifically, limiting the spread undermines fundamental goals of most open source projects, including that the project be accessible to all, that others use the project, and that a broad enough user base develops to help maintain and grow the project.

I should note that while downside (1) always applies, downsides (2) and (3) have some implied premises which vary by context. If those around you won’t be disturbed, then (2) doesn’t apply. If the goals of your project aren’t undermined by limiting the project’s spread, then (3) doesn’t apply.

A list of projects with vulgar names:

Of course more exist, such as Ubuntu Satanic Edition, but they are niche and not worth tracking.

Email: lorenzohess@tutanota.com

Created: 2026-02-01 Sun 22:46