It's trendy. If you don't like it, you can go write some go in go. Contribute to a thread on Threads. Write a factory with Factory. Write your reflections in Reflect. Keep in the loop on Loop while you recall what you did with Recall. So many choices.
It's trendy. If you don't like it, you can go write some go in go. Contribute to a thread on Threads. Write a factory with Factory. Write your reflections in Reflect. Keep in the loop on Loop while you recall what you did with Recall. So many choices.
Why not evaluate them on the merits? Is the name really the thing that’s important here?
“GitHub has so many outages, but dammit, that other one has a terrible name, it’s practically unusable”.
And origin is a pretty great name to give a git hosting platform. And do you think GitHub, Gitlab are original?
This is a great name! It ties back to git nicely (git pull origin/main), and sounds human.
Cursor was also a great name given that it evolved into an advanced AI assisted auto complete. I think their team does a solid job with naming.
Then google the names and look what comes up.
Without additional search terms you get the wrong results.
A word that is already used in computer is a bad name.
And with AI it won’t get better. Ambiguity is a source of confusion and mistakes.
By your logic pull/push/main are also great names.
One main purpose of a name is distinguishability.
If you google Cursor they dominate the whole first page
Surely they have a chance of doing it again with Origin
> Without additional search terms you get the wrong results.
Until the entity becomes popular enough, like I just searched for "stripe" and all visible results were about the payment company.