Skip to content
This repository was archived by the owner on May 1, 2025. It is now read-only.
This repository was archived by the owner on May 1, 2025. It is now read-only.

JA3... really? I don't think this name is vague enough. We can do better. #86

@825i

Description

@825i

So you arrived at the name JA3. Honestly, I'm not impressed guys. I don't think this name is ambiguous enough. I think we can do better.

I propose that we change the name from JA3 to XZ8. I think if Salesforce wants to stay a leader in CRM, you need to think even harder about using acronyms and names that are even more difficult to recognise. I mean what is the point otherwise? If we are going to go with JA3, why don't we go all in?

Look. I'm sorry John Althouse ,Jeff Atkinson, and Josh Atkins but this name just doesn't cut it. If you want people to adopt this, you have to make the name even more mysterious, more vague and more ambiguous. If I only need to dig through 15 pages in my favourite search engine, to figure out why you ran with this awful name, then clearly someone wasn't trying hard enough.

No really, in all seriousness. What compels 3 people to name something so badly (even if it is after themselves) when it could be revolutionary?
Can you imagine if Linus Torvalds had decided to name his OS "LT1"?

If you truly care about adoption and visibility. Rename the project. Especially as it's now evolved past the neckbeard-joke-phase.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions