this post was submitted on 11 Jul 2023
2911 points (98.6% liked)
Memes
45131 readers
1676 users here now
Rules:
- Be civil and nice.
- Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Lemmy isn't a lot better, tbh.
Also Kbin is a terrible name too. They really don't understand branding and accessibility in these new "grass-roots" apps.
Is reddit a great name? I don't think so. How about TikTok? Nah. It's about the product and its popularity. The name only needs to get you to the product. Past that the name doesn't matter.
It could be named dgoSh1t.biz and if it attracted the "cool kids", worked well, and filled a need it would take off.
@confusedbytheBasics @Emu short and distinctive names tend to be coveted. I guess because easier to discovery / remember / protect via copyright? Idk but there must be a reason basically ALL products that become dominant are 2 or 3 syllables names that are not (usually) normal words. Definitely a trend but NOT a rule
In which case kBin and Lemmy are fine names. Yeah?
@confusedbytheBasics In my opinion yes. Kbin more so than Lemmy and Mastodon.
Devs tend to suck at coming up with names. Microsoft is particularly rubbish at this.
Was Twitter a bad name?
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.
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.
Yes, but at least it's short, easy to remember and unambiguous when someone search it on Google.