It was originally going to be called twttr. Facebook was initially called FaceMash. Intel was originally going to be called Moore Noyce (founders being Gordon Moore and Robert Noyce) but the idea was scrapped because it sounded like "More Noise."

It's not just company names and products though. I work with the .NET stack and related technologies, and Microsoft has found like a billion different uses for the term "Razor" and derivatives thereof.

• Razor, a templating language used to generate HTML in C#, for example in ASP.NET MVC
  • Also the name of the parser of said templating code
• Razor Pages, a MVVM approach to ASP.NET, typically uses Razor, but isn't Razor. Could use something other than Razor too, but would still be Razor Pages.
• Blazor, a framework with which to build web applications, using Razor
  • Blazor Server, an application hosted (and rendered) on the server using SignalR to push changes to the client
  • Blazor WASM, an application downloaded to the client, running .NET in WebAssembly, rendering changes in the client before pushing to the DOM
  • Blazor United, a mixture of the two above! This is cutting edge stuff and not out yet.

Now, you (can) write Razor Pages, and regular ASP.NET MVC applications using Razor, but a page written in Razor isn't necessarily a Razor Page. You also use Razor when building components in Blazor, and you can embed Blazor components in Razor Pages, or even host Blazor applications on a Razor Page. However, a Blazor application isn't a Razor Page, and while they all use Razor, none of them are Razor.

There's also Blazor Hybrid, and the ability to use Blazor components in native applications. I'm actually doing this right now on a project at work; I'm writing a Blazor Server application, with a shared Razor Component Library, containing Blazor Components, which I use both in the Blazor Server application, and in the .NET MAUI Blazor Hybrid application for Windows/iOS/Android.